Triple
T9106178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Oil of California |
E218482
|
entity |
| Predicate | roleInAramco |
P87182
|
FINISHED |
| Object | founding shareholder |
—
|
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: founding shareholder | Statement: [Standard Oil of California, roleInAramco, founding shareholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAramco Context triple: [Standard Oil of California, roleInAramco, founding shareholder]
-
A.
roleInArabia
Indicates that an entity holds or held a specific role, position, or function within the context of Arabia.
-
B.
roleInUAE
Indicates that an entity holds or has held a specific role, position, or function within the United Arab Emirates.
-
C.
roleWithinBoeing
Indicates that one entity holds or has held a specific role, position, or function within the organization Boeing.
-
D.
roleInAirbus
Indicates that an entity holds or has held a specific role or position within Airbus.
-
E.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57286a88190b256d2461c5c0aed |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:16 p.m.