Triple
T23168930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebron oil field |
E578789
|
entity |
| Predicate | projectSanctionYear |
P7919
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Hebron oil field, projectSanctionYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectSanctionYear Context triple: [Hebron oil field, projectSanctionYear, 2012]
-
A.
coSanctionedSince
Indicates that two or more entities have jointly imposed or been subject to a sanction starting from a specified point in time and continuing thereafter.
-
B.
authorizationYear
chosen
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
C.
suppressionYear
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
-
D.
isSanctionedBy
Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
-
E.
crossErectedInYear
Indicates that a particular cross was erected or put in place in a specified year.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2e5e208190839ec37de4b974af |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.