Triple
T33263122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Transport and Trading Company |
E851575
|
entity |
| Predicate | sharesClass |
P5725
|
FINISHED |
| Object | Shell Transport and Trading Company plc shares |
—
|
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: Shell Transport and Trading Company plc shares | Statement: [Shell Transport and Trading Company, sharesClass, Shell Transport and Trading Company plc shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesClass Context triple: [Shell Transport and Trading Company, sharesClass, Shell Transport and Trading Company plc shares]
-
A.
sharesType
Indicates that two or more entities have the same type or belong to the same category.
-
B.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesTypeWith
Indicates that two entities belong to the same type or category.
-
E.
hasShareClass
chosen
Indicates that an entity is associated with a specific class or category of shares that defines distinct rights or characteristics of ownership.
- 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_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: May 1, 2026, 1:32 a.m.