Triple
T13585601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eyke |
E324549
|
entity |
| Predicate | liesToThe |
P110172
|
FINISHED |
| Object | east of Woodbridge |
—
|
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: east of Woodbridge | Statement: [Eyke, liesToThe, east of Woodbridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesToThe Context triple: [Eyke, liesToThe, east of Woodbridge]
-
A.
liesIn
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
B.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
C.
hasLie
Indicates that an entity is associated with or responsible for a specific lie or false statement.
-
D.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
E.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb03310fc819092a56b9f2d73f560 |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.