Triple
T22172125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Suite |
E547947
|
entity |
| Predicate | hasSettingInIndustry |
P147249
|
FINISHED |
| Object | furniture industry |
—
|
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: furniture industry | Statement: [Executive Suite, hasSettingInIndustry, furniture industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingInIndustry Context triple: [Executive Suite, hasSettingInIndustry, furniture industry]
-
A.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
B.
hasIndustrySection
Indicates that an entity belongs to, is categorized under, or is associated with a particular industry section.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
hasCustomerIndustry
Indicates that a customer is associated with or operates within a particular industry or sector.
-
E.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
- F. None of above. chosen
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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a69c12c8190a03177b5b740456a |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:34 p.m.