Triple
T10181667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Monorail Co., Ltd. |
E236799
|
entity |
| Predicate | railwayTypeOperated |
P38622
|
FINISHED |
| Object | monorail |
—
|
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: monorail | Statement: [Osaka Monorail Co., Ltd., railwayTypeOperated, monorail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTypeOperated Context triple: [Osaka Monorail Co., Ltd., railwayTypeOperated, monorail]
-
A.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
B.
operatedOnRailroad
Indicates that an entity conducted operations or provided services on a railroad system.
-
C.
railwayCompanyType
chosen
Indicates the specific category or classification of a railway company in terms of its role, ownership, or operational type.
-
D.
hasLocalRailOperator
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
-
E.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
- 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.