Triple
T37771858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kokura |
E941569
|
entity |
| Predicate | monorailOperator |
P189021
|
FINISHED |
| Object | Kitakyushu Urban Monorail Co., Ltd. |
—
|
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: Kitakyushu Urban Monorail Co., Ltd. | Statement: [Kokura, monorailOperator, Kitakyushu Urban Monorail Co., Ltd.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monorailOperator Context triple: [Kokura, monorailOperator, Kitakyushu Urban Monorail Co., Ltd.]
-
A.
monorailStation
Indicates that an entity functions as a station or stop specifically for a monorail transit system.
-
B.
monorailUse
Indicates that one entity makes use of, travels on, or is transported by a monorail system in relation to another entity or context.
-
C.
trainOperator
Indicates that one entity operates, manages, or runs train services for another entity or within a specific rail system.
-
D.
cableCarOperator
Indicates that one entity operates, manages, or runs a cable car service for another entity or location.
-
E.
tramOperator
Indicates that one entity operates, manages, or runs tram services for another entity or area.
- F. None of above. chosen
Provenance (4 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.