Triple
T2997816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamatoji Line |
E81112
|
entity |
| Predicate | usesRouteNameFor |
P40317
|
FINISHED |
| Object | section of Kansai Main Line |
—
|
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: section of Kansai Main Line | Statement: [Yamatoji Line, usesRouteNameFor, section of Kansai Main Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRouteNameFor Context triple: [Yamatoji Line, usesRouteNameFor, section of Kansai Main Line]
-
A.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
isStandardRouteOn
chosen
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
C.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
D.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
E.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f612148190a5a565ba2ecc4fc0 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.