Triple
T28200573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E3 series Shinkansen |
E716870
|
entity |
| Predicate | serviceOperatorRegion |
P30177
|
FINISHED |
| Object | Tohoku region |
—
|
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: Tohoku region | Statement: [E3 series Shinkansen, serviceOperatorRegion, Tohoku region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceOperatorRegion Context triple: [E3 series Shinkansen, serviceOperatorRegion, Tohoku region]
-
A.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
B.
serviceRegion
chosen
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
C.
regionalServiceOperational
Indicates that a service is currently functioning and available within a specified geographic region.
-
D.
operatedInRegion
Indicates that an entity conducted operations or activities within a specified geographic region.
-
E.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 10:31 p.m.