Triple
T36923271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Fischer |
E913265
|
entity |
| Predicate | inUniverseCompanyType |
P100243
|
FINISHED |
| Object | energy 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: energy conglomerate | Statement: [Robert Fischer, inUniverseCompanyType, energy conglomerate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseCompanyType Context triple: [Robert Fischer, inUniverseCompanyType, energy conglomerate]
-
A.
inUniverseOrganization
Indicates that an organization exists and operates within a specified fictional or narrative universe.
-
B.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
C.
inUniverseAffiliationType
Indicates the type or category of affiliation an entity has within a particular fictional or narrative universe.
-
D.
belongsToCompanyType
chosen
Indicates that an entity is associated with or classified under a particular type or category of company.
-
E.
inUniverseWorkplaceRole
Indicates that an entity holds a specific workplace role or job position within a fictional or narrative universe.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:13 p.m.