Triple
T15343377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petronas Carigali Sdn Bhd |
E366853
|
entity |
| Predicate | exploresResource |
P1857
|
FINISHED |
| Object | crude oil |
—
|
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: crude oil | Statement: [Petronas Carigali Sdn Bhd, exploresResource, crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresResource Context triple: [Petronas Carigali Sdn Bhd, exploresResource, crude oil]
-
A.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
-
B.
explores
chosen
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
C.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
D.
explorationUse
Indicates the use of something specifically for exploration or investigative activities.
-
E.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e163a3c8190ab933411372c1573 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.