Triple
T15270918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junín |
E365016
|
entity |
| Predicate | reserveType |
P50114
|
FINISHED |
| Object | proven extra-heavy oil reserves |
—
|
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: proven extra-heavy oil reserves | Statement: [Junín, reserveType, proven extra-heavy oil reserves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reserveType Context triple: [Junín, reserveType, proven extra-heavy oil reserves]
-
A.
reservationProvision
Indicates that one entity provides, allocates, or sets aside a reservation (such as a booked resource, service slot, or capacity) for another entity.
-
B.
typeOfReserve
chosen
Indicates that one entity is classified as a specific kind or category of reserve in relation to another entity.
-
C.
reservationIn
Indicates that a reservation is associated with, or booked for, a specific place, service, or resource.
-
D.
reserveName
Indicates that an entity secures or sets aside a specific name so that it cannot be used by others.
-
E.
reservationState
Indicates the current status or phase of a reservation within its lifecycle (e.g., pending, confirmed, canceled, completed).
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0094eac848190a1740ae1aa6b28e0 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.