Triple
T31901382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxenhope railway station |
E814430
|
entity |
| Predicate | hasCoalFacilities |
P120102
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oxenhope railway station, hasCoalFacilities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoalFacilities Context triple: [Oxenhope railway station, hasCoalFacilities, true]
-
A.
hasCoalMiningCompany
Indicates that an entity is associated with or owns a company whose primary business is coal mining.
-
B.
hasCoalBasin
Indicates that one entity contains, includes, or is characterized by a coal-bearing geological basin associated with the other entity.
-
C.
hasCoalMineNearby
chosen
Indicates that a location or entity is situated close to at least one coal mine.
-
D.
majorCoalField
Indicates that a location is recognized as a principal or highly significant coal-producing field within a region or country.
-
E.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a03352bb9688190b965d188769fcacd |
completed | May 12, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_6a033329ae5c81909532843fe716ec77 |
completed | May 12, 2026, 2:03 p.m. |
Created at: April 30, 2026, 11:59 p.m.