Triple
T10181697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Monorail Co., Ltd. |
E236799
|
entity |
| Predicate | railInfrastructureType |
P63327
|
FINISHED |
| Object | elevated guideway |
—
|
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: elevated guideway | Statement: [Osaka Monorail Co., Ltd., railInfrastructureType, elevated guideway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railInfrastructureType Context triple: [Osaka Monorail Co., Ltd., railInfrastructureType, elevated guideway]
-
A.
hasRailwayInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific type or category of railway infrastructure.
-
B.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
railCorridorType
Indicates the specific classification or type of a rail corridor associated with the subject (e.g., mainline, branch line, high-speed, freight, etc.).
-
D.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
E.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded32b91c8190b01ad37b2456080a |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.