Triple
T22801583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oost Gelre |
E564406
|
entity |
| Predicate | ZwarteCrossLocation |
P149769
|
FINISHED |
| Object | Lichtenvoorde |
—
|
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: Lichtenvoorde | Statement: [Oost Gelre, ZwarteCrossLocation, Lichtenvoorde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ZwarteCrossLocation Context triple: [Oost Gelre, ZwarteCrossLocation, Lichtenvoorde]
-
A.
crossesNear
Indicates that one entity passes across the path or area of another entity at a location that is close to, but not directly intersecting, the other entity.
-
B.
locatedAtIntersectionOf
Indicates that something is situated at the point where two or more paths, roads, or boundaries cross or meet.
-
C.
locationDuring_Operation Crossroads
Indicates that an entity was located at a particular place during the time period of Operation Crossroads.
-
D.
crossesIn
Indicates that one entity passes over or through the path, boundary, or area occupied by another entity, intersecting its space or trajectory.
-
E.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of another entity.
- F. None of above. chosen
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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdd87648190ba30f0b8f3ef7346 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:31 p.m.