Triple
T24761945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea copper industry |
E619469
|
entity |
| Predicate | hadMajorWorks |
P6260
|
FINISHED |
| Object | Morfa Copperworks |
—
|
NE NERFINISHED |
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: Morfa Copperworks | Statement: [Swansea copper industry, hadMajorWorks, Morfa Copperworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorWorks Context triple: [Swansea copper industry, hadMajorWorks, Morfa Copperworks]
-
A.
hasMainWorks
Indicates that an entity possesses or is associated with one or more primary or most significant works.
-
B.
eraOfMajorWorks
Indicates the historical period during which an entity produced its most significant or influential works.
-
C.
hasMajorWork
chosen
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
-
D.
hasCreatedWorksFor
Indicates that one entity has produced or created works (such as art, documents, or products) on behalf of or for the benefit of another entity.
-
E.
majorWorkAboutHim
Indicates that a major work (such as a book, film, or study) is primarily about the referenced person.
- 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_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:27 a.m.