Triple
T33180974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chikuho Main Line |
E849324
|
entity |
| Predicate | formerIndustryServed |
P129420
|
FINISHED |
| Object | coal mining |
—
|
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: coal mining | Statement: [Chikuho Main Line, formerIndustryServed, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIndustryServed Context triple: [Chikuho Main Line, formerIndustryServed, coal mining]
-
A.
formerKeyIndustry
chosen
Indicates that an entity was once a primary or strategically important industry for another entity but no longer holds that status.
-
B.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
respondentIndustry
Indicates the industry or sector in which the respondent operates or is employed.
-
D.
hasIndustryRole
Indicates that an entity holds or performs a specific role, function, or position within a particular industry or sector.
-
E.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:29 a.m.