Triple
T17102410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tama area |
E415010
|
entity |
| Predicate | hasTransport |
P1298
|
FINISHED |
| Object | Tama Monorail |
E193100
|
NE 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: Tama Monorail | Statement: [Tama area, hasTransport, Tama Monorail]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tama Monorail Context triple: [Tama area, hasTransport, Tama Monorail]
-
A.
Tama Monorail
chosen
Tama Monorail is a straddle-beam monorail line in Tokyo, Japan, providing urban transit service through the Tama area.
-
B.
Hitachi Monorail
Hitachi Monorail is a Japanese monorail system developed by Hitachi, Ltd., widely used in urban transit lines in Japan and abroad for its reliable, straddle-beam design.
-
C.
Tokyo Monorail
Tokyo Monorail is an urban transit line in Tokyo that provides rapid rail service between central Tokyo and Haneda Airport.
-
D.
KL Monorail
KL Monorail is an elevated urban rail line in Kuala Lumpur that provides rapid transit service through the city’s central and commercial districts.
-
E.
Osaka Monorail
Osaka Monorail is a straddle-beam monorail system in Osaka Prefecture, Japan, serving as a major urban transit line linking key suburbs, commercial areas, and transport hubs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2495c88190b5b16a006a994faf |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139fdda488190a1ca5c7ca875e044 |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:35 a.m.