Triple
T34133064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lixhe |
E875480
|
entity |
| Predicate | hasRegionLevel |
P285
|
FINISHED |
| Object | Wallonia |
E21626
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Wallonia | Statement: [Lixhe, hasRegionLevel, Wallonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionLevel Context triple: [Lixhe, hasRegionLevel, Wallonia]
-
A.
hasHigherLevelRegion
Indicates that one region is geographically or administratively contained within and subordinate to a larger, higher-level region.
-
B.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
hasCountrySubdivisionLevel
Indicates the hierarchical administrative level or tier at which a given country subdivision (such as a state, province, or region) is defined within the country's overall territorial organization.
-
D.
hierarchicalLevelInRegion
Indicates the relative rank or position an entity holds within a defined regional or geographic hierarchy.
-
E.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bc4f7108190aefaf59c1a4824d5 |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.