Triple
T15357668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of Octan |
E367203
|
entity |
| Predicate | companyTypeGoverned |
P118252
|
FINISHED |
| Object | conglomerate |
—
|
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: conglomerate | Statement: [President of Octan, companyTypeGoverned, conglomerate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyTypeGoverned Context triple: [President of Octan, companyTypeGoverned, conglomerate]
-
A.
organizationTypeGoverned
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
-
B.
governingCompany
Indicates that one company exercises control, authority, or management over another company.
-
C.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
D.
governmentTypeRegulated
Indicates that the type or form of government of an entity is subject to regulation, control, or definition by another authority or governing framework.
-
E.
organizationType
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2d4934819097fc63603964217c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:18 a.m.