Triple
T11334672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundonald |
E268438
|
entity |
| Predicate | hasFormerNearbyIndustry |
P3008
|
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: [Dundonald, hasFormerNearbyIndustry, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerNearbyIndustry Context triple: [Dundonald, hasFormerNearbyIndustry, coal mining]
-
A.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
B.
hasFormerUseNearby
Indicates that something in the vicinity previously had a particular use or function that is no longer current.
-
C.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
D.
hasMajorCompanyNearby
Indicates that a location or entity is situated close to at least one large or significant company.
-
E.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.