Triple
T32174671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smurfit |
E821806
|
entity |
| Predicate | notableCompanyAssociatedWith |
P152330
|
FINISHED |
| Object | Smurfit Kappa |
E1763771
|
NE 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: Smurfit Kappa | Statement: [Smurfit, notableCompanyAssociatedWith, Smurfit Kappa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompanyAssociatedWith Context triple: [Smurfit, notableCompanyAssociatedWith, Smurfit Kappa]
-
A.
notableEmployer
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
B.
associatedCompanyKnownFor
chosen
Indicates that a company linked to an entity is recognized or notable for a particular product, service, activity, or characteristic.
-
C.
associatedCompanyNotableRole
Indicates that an entity has a notable role or position in a specified associated company.
-
D.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
-
E.
notableCompanyFoundedIn
Indicates that a company is recognized as notable and was founded in the specified location or time period.
- F. None of above.
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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bdd4ef081909d86b93410286eea |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.