Triple
T739011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Paper |
E15200
|
entity |
| Predicate | hasKeyCustomerSector |
P4053
|
FINISHED |
| Object | e-commerce |
—
|
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: e-commerce | Statement: [International Paper, hasKeyCustomerSector, e-commerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyCustomerSector Context triple: [International Paper, hasKeyCustomerSector, e-commerce]
-
A.
hasKeyOrganization
Indicates that an entity is associated with or primarily represented by a main or primary organization.
-
B.
hasKeyAgency
Indicates that an entity serves as the primary responsible or controlling agency for another entity, action, or process.
-
C.
hasKeyInstitutionType
Indicates that an entity is associated with a specific type or category of key institution.
-
D.
keySector
chosen
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
-
E.
hasStakeholder
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.