Triple
T38157750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakubi Line |
E952931
|
entity |
| Predicate | notableLimitedExpress |
P1669
|
FINISHED |
| Object | Yakumo |
E1983178
|
NE 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: Yakumo | Statement: [Hakubi Line, notableLimitedExpress, Yakumo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLimitedExpress Context triple: [Hakubi Line, notableLimitedExpress, Yakumo]
-
A.
hasLimitedExpressBrand
Indicates that an entity possesses or is associated with a Limited Express brand designation or service.
-
B.
notableTrain
chosen
Indicates that there is a train or rail service associated with the subject that is considered notable or significant in some way.
-
C.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
D.
notableTrainBrand
Indicates that an entity is a well-known or significant brand associated with trains or railway services.
-
E.
notableCargo
Indicates that an entity is known for carrying or having carried a particularly important, famous, or otherwise noteworthy cargo.
- F. None of above.
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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a8271f970a8819088f69101bc8305b8 |
completed | Aug. 17, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.