Triple
T31677772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metro 9000 series EMU |
E808448
|
entity |
| Predicate | operatesThroughServiceOnLine |
P15252
|
FINISHED |
| Object | Tokyu Meguro Line |
—
|
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: Tokyu Meguro Line | Statement: [Tokyo Metro 9000 series EMU, operatesThroughServiceOnLine, Tokyu Meguro Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesThroughServiceOnLine Context triple: [Tokyo Metro 9000 series EMU, operatesThroughServiceOnLine, Tokyu Meguro Line]
-
A.
operatesOnlineService
Indicates that an entity runs or manages an online service or platform for others to use.
-
B.
operatesOnLine
chosen
Indicates that an entity conducts operations, services, or activities along a specific line or route.
-
C.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
D.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
E.
openedForServiceOnLine
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: April 30, 2026, 11:03 p.m.