Triple
T9745965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harajuku Station |
E236307
|
entity |
| Predicate | locatedOnLoopLine |
P2409
|
FINISHED |
| Object | Yamanote Line |
—
|
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: Yamanote Line | Statement: [Harajuku Station, locatedOnLoopLine, Yamanote Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnLoopLine Context triple: [Harajuku Station, locatedOnLoopLine, Yamanote Line]
-
A.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
B.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
C.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
isOnLoopLine
Indicates that one entity (typically a route, track, or segment) lies on or belongs to a loop-shaped line or circuit within a network.
-
E.
positionOnLine
Indicates that one entity occupies a specific location along a defined line or linear path in relation to another.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f65ad788190b68d731b6f516d93 |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.