Triple
T33263127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Transport and Trading Company |
E851575
|
entity |
| Predicate | coParentOf |
P79759
|
FINISHED |
| Object | Royal Dutch Shell Group |
—
|
NE NERFINISHED |
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: Royal Dutch Shell Group | Statement: [Shell Transport and Trading Company, coParentOf, Royal Dutch Shell Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coParentOf Context triple: [Shell Transport and Trading Company, coParentOf, Royal Dutch Shell Group]
-
A.
coParentWith
chosen
Indicates that two individuals share at least one child together, jointly occupying a parental role for that child.
-
B.
unwillingParentOf
Indicates a parental relationship in which the parent does not willingly or voluntarily assume the role or responsibilities toward the child.
-
C.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
D.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
E.
parentsStatus
Indicates the marital or relational status between a person's parents (e.g., married, divorced, separated, single).
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.