Triple
T32959284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostelijke Ourthe |
E843187
|
entity |
| Predicate | ligtInGewest |
P103735
|
FINISHED |
| Object | Wallonië |
—
|
NE NERFINISHED |
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: Wallonië | Statement: [Oostelijke Ourthe, ligtInGewest, Wallonië]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ligtInGewest Context triple: [Oostelijke Ourthe, ligtInGewest, Wallonië]
-
A.
ligtInLand
Indicates that one place or region is geographically located within the boundaries of a specific country.
-
B.
heldInProvince
Indicates that an event or activity takes place within the boundaries of a specified province.
-
C.
isInPolderRegion
Indicates that one entity is located within a polder region, i.e., land reclaimed from a body of water and typically protected by dikes.
-
D.
isLocatedInSubdivision
chosen
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
-
E.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
- F. None of above.
Provenance (3 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:21 a.m.