Triple
T21752414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRGY |
E536946
|
entity |
| Predicate | industryGroup |
P24922
|
FINISHED |
| Object | Packaged foods and meats |
—
|
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: Packaged foods and meats | Statement: [NSRGY, industryGroup, Packaged foods and meats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryGroup Context triple: [NSRGY, industryGroup, Packaged foods and meats]
-
A.
industryStart
Indicates the point in time or event at which an industry, industrial activity, or industrial era begins.
-
B.
industryConsortium
Indicates a collaborative association where multiple organizations formally join together within an industry to pursue shared goals, standards, or initiatives.
-
C.
industryContext
chosen
Indicates the industry or sector within which an entity, activity, or relationship is situated or most relevant.
-
D.
industryIntegrated
Indicates that something is closely connected or coordinated with industry practices, partners, or environments, often through collaboration, alignment, or direct involvement.
-
E.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8b8b9c8190b1f6a8bc25d69dbb |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.