Triple
T4930431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPQ |
E110679
|
entity |
| Predicate | associatedCompanySector |
P6744
|
FINISHED |
| Object | technology sector |
—
|
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: technology sector | Statement: [CPQ, associatedCompanySector, technology sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanySector Context triple: [CPQ, associatedCompanySector, technology sector]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
associatedWithEconomicSector
Indicates that an entity has a connection or involvement with a particular economic sector, such as operating, participating, or being relevant within that sector.
-
C.
industryOfUnderlyingCompany
chosen
Indicates the industry sector in which the underlying company associated with this entity operates.
-
D.
hasParentCompanyIndustry
Indicates that an entity’s parent company operates in, or is associated with, a specified industry.
-
E.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd703a0fa48190809b6ac3f2731349 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.