Triple
T31601189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Texas oil boom |
E806351
|
entity |
| Predicate | discoveryWell |
P135093
|
FINISHED |
| Object | Daisy Bradford No. 3 |
—
|
NE NERFINISHED |
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: Daisy Bradford No. 3 | Statement: [East Texas oil boom, discoveryWell, Daisy Bradford No. 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryWell Context triple: [East Texas oil boom, discoveryWell, Daisy Bradford No. 3]
-
A.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
B.
discoveryScope
Indicates the extent or range within which something can be found, detected, or identified.
-
C.
discoveryTarget
chosen
Indicates that one entity is the object, subject, or focus that another entity discovers or aims to discover.
-
D.
discoverySurvey
Indicates that an entity conducts or is associated with an initial exploratory survey or assessment to gather foundational information.
-
E.
discoveryMethod
Indicates the process, technique, or approach by which something was found, detected, or identified.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 10:32 p.m.