Triple
T24761949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swansea copper industry |
E619469
|
entity |
| Predicate | hadMajorCompany |
P158106
|
FINISHED |
| Object | Williams Foster & Co. |
—
|
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: Williams Foster & Co. | Statement: [Swansea copper industry, hadMajorCompany, Williams Foster & Co.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMajorCompany Context triple: [Swansea copper industry, hadMajorCompany, Williams Foster & Co.]
-
A.
hadMajorCompany
chosen
Indicates that an entity previously owned, led, or was primarily associated with a major company.
-
B.
hasMajorCompanyOrigin
Indicates that an entity originates from, was founded by, or initially developed within a major company.
-
C.
hadCompanyAt
Indicates that an entity was accompanied by or in the presence of another entity at a specific time or place.
-
D.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
E.
hasMajorOrganization
Indicates that an entity is associated with or primarily represented by a major organization.
- 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_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:27 a.m.