Triple
T24761928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea copper industry |
E619469
|
entity |
| Predicate | madeSwansea |
P157100
|
FINISHED |
| Object | global hub of copper smelting |
—
|
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: global hub of copper smelting | Statement: [Swansea copper industry, madeSwansea, global hub of copper smelting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeSwansea Context triple: [Swansea copper industry, madeSwansea, global hub of copper smelting]
-
A.
movedHeadquartersToLlantrisant
Indicates that an entity relocated its main headquarters to Llantrisant.
-
B.
replacedInWalesBy
Indicates that something previously in use or effect in Wales has been superseded or substituted by another specific thing.
-
C.
SouthamptonManager
Indicates that the subject serves as the manager (head coach) of the football club Southampton.
-
D.
communityWales
Indicates a relationship where an entity is associated with, belongs to, or is situated within the community of Wales.
-
E.
succeededByAsMPForCeredigion
Indicates that one individual was later succeeded by another as the Member of Parliament representing the constituency of Ceredigion.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:27 a.m.