Triple
T35909046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0 series Shinkansen |
E1038553
|
entity |
| Predicate | enteredServiceForEvent |
P185705
|
FINISHED |
| Object | 1964 Tokyo Olympics |
—
|
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: 1964 Tokyo Olympics | Statement: [0 series Shinkansen, enteredServiceForEvent, 1964 Tokyo Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceForEvent Context triple: [0 series Shinkansen, enteredServiceForEvent, 1964 Tokyo Olympics]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceBefore
Indicates that one entity began its period of service earlier in time than another entity.
-
C.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
-
D.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
E.
enteredServiceRole
Indicates that an entity has begun serving in a particular role, position, or capacity.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:07 p.m.