Triple
T35639549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 道央自動車道 |
E1029819
|
entity |
| Predicate | operatorAbbrev |
P152086
|
FINISHED |
| Object | NEXCO東日本 |
—
|
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: NEXCO東日本 | Statement: [道央自動車道, operatorAbbrev, NEXCO東日本]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAbbrev Context triple: [道央自動車道, operatorAbbrev, NEXCO東日本]
-
A.
otherOperatorAbbreviation
Indicates that one operator is referred to or represented by an alternative abbreviated form used by another operator.
-
B.
alternativeAbbreviation
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
C.
ownerAbbreviation
Indicates that one entity is an abbreviated or shortened form of the name or designation of another entity that owns or is primarily associated with it.
-
D.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
E.
abbreviationUsedBy
chosen
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:05 p.m.