Triple
T25202814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Forks Formation |
E631164
|
entity |
| Predicate | discoveredAsMajorPlay |
P158029
|
FINISHED |
| Object | early 2000s |
—
|
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 2000s | Statement: [Three Forks Formation, discoveredAsMajorPlay, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredAsMajorPlay Context triple: [Three Forks Formation, discoveredAsMajorPlay, early 2000s]
-
A.
isMajorShowOf
Indicates that one entity is the primary or most prominent show or production associated with another entity.
-
B.
firstMajorDiscovery
Indicates that the object is the earliest significant discovery or breakthrough associated with the subject.
-
C.
hasMajorFranchise
Indicates that an entity possesses or is associated with a primary, large-scale franchise within a broader domain or organization.
-
D.
isMajorHit
Indicates that something (such as a work, product, or performance) has achieved a high level of success, popularity, or impact.
-
E.
isMajorHighlightOf
Indicates that something serves as a primary or especially notable feature, event, or focal point within a larger context or whole.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474ba127c819086f8f0c698a1bb4d |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:51 p.m.