Triple
T14677085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midlothian, Virginia |
E344672
|
entity |
| Predicate | earliestCoalMining |
P113262
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Midlothian, Virginia, earliestCoalMining, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestCoalMining Context triple: [Midlothian, Virginia, earliestCoalMining, 18th century]
-
A.
hasCoalMiningHistory
Indicates that an entity has a past or ongoing involvement in coal mining activities or industry.
-
B.
miningHeritage
Indicates a historical or cultural connection to mining activities, sites, or traditions.
-
C.
earliestPermanentSettlement
Indicates that one entity is the location or instance of the first long-term, continuously inhabited settlement associated with another entity.
-
D.
earliestKnownPeriod
chosen
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
E.
collieryOpened
Indicates that a colliery (coal mine) was opened or began operations.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb567c2b88190a9639e61b6fba7df |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.