Triple
T19238952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaca Muerta shale formation |
E481077
|
entity |
| Predicate | unconventionalDevelopmentStart |
P11886
|
FINISHED |
| Object | early 2010s |
—
|
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: early 2010s | Statement: [Vaca Muerta shale formation, unconventionalDevelopmentStart, early 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unconventionalDevelopmentStart Context triple: [Vaca Muerta shale formation, unconventionalDevelopmentStart, early 2010s]
-
A.
initiationPractice
Indicates the act of beginning, launching, or formally starting a particular practice, process, or activity.
-
B.
developmentStart
chosen
Indicates the point in time or event when the development process of something begins.
-
C.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
-
D.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
E.
developsUntil
Indicates that a process, condition, or entity continues to develop or progress up to a specified point or limit in time or state.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faef827c81909157bbcd4060dfc9 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.