Triple
T26062309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KO |
E657292
|
entity |
| Predicate | associatedLineName |
P103597
|
FINISHED |
| Object | Keiō New 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: Keiō New Line | Statement: [KO, associatedLineName, Keiō New Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLineName Context triple: [KO, associatedLineName, Keiō New Line]
-
A.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
B.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
formerLineName
Indicates that the object is a previous or former name by which the referenced line was known.
-
D.
associatedWithTransitLine
chosen
Indicates that an entity has a connection or linkage to a specific transit line, such as being part of, served by, or otherwise related to that line.
-
E.
lineName
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 26, 2026, 7:19 p.m.