Triple
T25016716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamabiko |
E626154
|
entity |
| Predicate | introducedAsServiceOn |
P152832
|
FINISHED |
| Object | Tōhoku Shinkansen |
—
|
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: Tōhoku Shinkansen | Statement: [Yamabiko, introducedAsServiceOn, Tōhoku Shinkansen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsServiceOn Context triple: [Yamabiko, introducedAsServiceOn, Tōhoku Shinkansen]
-
A.
introducedForServiceOn
chosen
Indicates that something was first put into official use or operation for a particular service on a specified date or occasion.
-
B.
introducedForServiceWith
Indicates that one entity was presented or brought to the attention of another entity specifically for the purpose of providing a service.
-
C.
introducedToService
Indicates that one entity has presented or brought another entity into contact with a particular service for the first time.
-
D.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
E.
providesServiceOn
Indicates that one entity offers or performs a service during, on, or in connection with a specified time, date, or schedule.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:06 a.m.