Triple
T29401429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santos Limited |
E745652
|
entity |
| Predicate | focusResource |
P179495
|
FINISHED |
| Object | natural gas for domestic markets |
—
|
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: natural gas for domestic markets | Statement: [Santos Limited, focusResource, natural gas for domestic markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusResource Context triple: [Santos Limited, focusResource, natural gas for domestic markets]
-
A.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
B.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
C.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
focusModel
Indicates that one entity serves as the primary or central model that another entity is directed toward, based on, or concentrated on.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 2:51 p.m.