Triple
T35238035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Company Limited |
E1017428
|
entity |
| Predicate | hasMajorOperatingDivision |
P7588
|
FINISHED |
| Object | Sobeys Inc. |
E329231
|
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: Sobeys Inc. | Statement: [Empire Company Limited, hasMajorOperatingDivision, Sobeys Inc.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorOperatingDivision Context triple: [Empire Company Limited, hasMajorOperatingDivision, Sobeys Inc.]
-
A.
hasBusinessDivision
chosen
Indicates that an organization includes or is composed of a specific business division as a subordinate unit.
-
B.
hasMajorOrganization
Indicates that an entity is associated with or primarily represented by a major organization.
-
C.
isMajorDivisionOf
Indicates that one entity is a primary or principal subdivision or section within another, larger entity.
-
D.
isMainDivisionOf
Indicates that one division functions as the primary or central division within, or in relation to, another organizational structure.
-
E.
hasServiceDivision
Indicates that an entity includes or is organized into a specific service-oriented division or department.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384019c80081908c26e626c7f73bbb |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: May 3, 2026, 4:02 p.m.