Triple
T35389744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carmaux |
E1022894
|
entity |
| Predicate | formerMainResource |
P28507
|
FINISHED |
| Object | coal |
—
|
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 | Statement: [Carmaux, formerMainResource, coal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMainResource Context triple: [Carmaux, formerMainResource, coal]
-
A.
formerMainExport
chosen
Indicates that something was once the primary export of a place or entity but no longer holds that status.
-
B.
originalResource
Indicates that one resource serves as the source, predecessor, or basis from which another resource is derived or adapted.
-
C.
centralResource
Indicates that one entity functions as the primary or core resource upon which another entity depends or is organized.
-
D.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
E.
formerUrl
Indicates that one entity was previously identified or accessible via the URL represented by the other entity, but that URL is no longer current.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: May 3, 2026, 4:03 p.m.