Triple
T32959289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostelijke Ourthe |
E843187
|
entity |
| Predicate | FranseNaam |
P6538
|
FINISHED |
| Object | Ourthe orientale |
—
|
LITERAL 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: Ourthe orientale | Statement: [Oostelijke Ourthe, FranseNaam, Ourthe orientale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FranseNaam Context triple: [Oostelijke Ourthe, FranseNaam, Ourthe orientale]
-
A.
nameInFrench
chosen
Indicates that an entity is known or referred to by a specific name expressed in the French language.
-
B.
WestFrisianName
Indicates that the associated name is the form used in the West Frisian language for the given entity.
-
C.
hasNameInDutch
Indicates that an entity is associated with a specific name or label expressed in the Dutch language.
-
D.
hasNameInWalloon
Indicates that an entity is associated with a specific name expressed in the Walloon language.
-
E.
hasNameInBelgium
Indicates that an entity is known or referred to by a particular name specifically within the context of Belgium.
- 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_69f6d17799888190a57b3e104bf5da6a |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.