Triple
T36034599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorachi Subprefecture |
E1042361
|
entity |
| Predicate | historicalCoalField |
P178259
|
FINISHED |
| Object | Sorachi coalfield |
—
|
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: Sorachi coalfield | Statement: [Sorachi Subprefecture, historicalCoalField, Sorachi coalfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCoalField Context triple: [Sorachi Subprefecture, historicalCoalField, Sorachi coalfield]
-
A.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
B.
majorCoalField
chosen
Indicates that a location is recognized as a principal or highly significant coal-producing field within a region or country.
-
C.
coalMinedFrom
Indicates that a quantity or batch of coal has been extracted from a particular source location, such as a mine or geological deposit.
-
D.
hasCoalBasin
Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
-
E.
hasCoalMiningCompany
Indicates that an entity is associated with or owns a company whose primary business is coal mining.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: May 3, 2026, 4:07 p.m.