Triple
T32959294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostelijke Ourthe |
E843187
|
entity |
| Predicate | gelegenOpContinent |
P118578
|
FINISHED |
| Object | Europa |
—
|
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: Europa | Statement: [Oostelijke Ourthe, gelegenOpContinent, Europa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gelegenOpContinent Context triple: [Oostelijke Ourthe, gelegenOpContinent, Europa]
-
A.
continentOfLocation
chosen
Indicates that one entity is the continent on which the other entity is geographically located.
-
B.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
-
C.
livedOnContinent
Indicates that an entity resided for a period of time on a specified continent.
-
D.
continentB
Indicates that the subject entity is a continent that contains or is associated with the object entity (such as a country, region, or location).
-
E.
continentFound
Indicates that a specified continent is the location where a particular entity is found or occurs.
- 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.