Triple
T13692057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakura |
E328289
|
entity |
| Predicate | serviceCategoryWithinJR |
P66133
|
FINISHED |
| Object | mid-range Shinkansen service |
—
|
LITERAL FINISHED |
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: mid-range Shinkansen service | Statement: [Sakura, serviceCategoryWithinJR, mid-range Shinkansen service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCategoryWithinJR Context triple: [Sakura, serviceCategoryWithinJR, mid-range Shinkansen service]
-
A.
publicServiceCategory
chosen
Indicates the classification or type of public service that an entity, activity, or offering belongs to.
-
B.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
C.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
-
D.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8746458819095ec1ba3c01ef31b |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.