Triple
T24761932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea copper industry |
E619469
|
entity |
| Predicate | reliedOnResource |
P22819
|
FINISHED |
| Object | local coal from South Wales coalfield |
—
|
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: local coal from South Wales coalfield | Statement: [Swansea copper industry, reliedOnResource, local coal from South Wales coalfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliedOnResource Context triple: [Swansea copper industry, reliedOnResource, local coal from South Wales coalfield]
-
A.
reliedOn
chosen
Indicates that one entity depends on another for support, resources, or functionality.
-
B.
basedOnResource
Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
-
C.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
D.
associatedWithResource
Indicates a relationship in which an entity is linked or connected to a particular resource, such that the resource is relevant or applicable to that entity.
-
E.
importedBy
Indicates that one entity brings another entity into a system, context, or location from an external source.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:27 a.m.