Triple
T9106377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghawar oil field |
E218486
|
entity |
| Predicate | resourceStatus |
P86514
|
FINISHED |
| Object | mature supergiant field |
—
|
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: mature supergiant field | Statement: [Ghawar oil field, resourceStatus, mature supergiant field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceStatus Context triple: [Ghawar oil field, resourceStatus, mature supergiant field]
-
A.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
B.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
C.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
D.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
E.
organizationalStatus
Indicates the current state or condition of an organization within a defined context, such as its operational, legal, or membership status.
- 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_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.