Triple
T14083576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series E5 Shinkansen |
E338930
|
entity |
| Predicate | topServiceBrand |
P34842
|
FINISHED |
| Object | Hayabusa 320 km/h 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: Hayabusa 320 km/h service | Statement: [Series E5 Shinkansen, topServiceBrand, Hayabusa 320 km/h service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topServiceBrand Context triple: [Series E5 Shinkansen, topServiceBrand, Hayabusa 320 km/h service]
-
A.
serviceBrand
chosen
Indicates that one entity is the brand under which a particular service is offered or marketed by another entity.
-
B.
competitiveBrandName
Indicates that one brand name is in a competitive relationship with another brand name in the same market or product space.
-
C.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
D.
favoriteBrand
Indicates that one entity is the preferred or most liked brand of another entity.
-
E.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ede40048190b465e909565730c1 |
completed | April 14, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.