Triple
T31384601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania oil rush |
E800561
|
entity |
| Predicate | inceptionSite |
P171676
|
FINISHED |
| Object | Drake Well |
—
|
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: Drake Well | Statement: [Pennsylvania oil rush, inceptionSite, Drake Well]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionSite Context triple: [Pennsylvania oil rush, inceptionSite, Drake Well]
-
A.
inception
Indicates the point in time or event at which something begins, originates, or is first established.
-
B.
inceptionPart
Indicates that one entity represents a component, segment, or phase within the initial creation or starting process of another entity.
-
C.
inceptionAsExpoSite
Indicates that a site came into existence or was formally established in connection with serving as an exposition venue.
-
D.
inceptionAsSymbol
Indicates that one entity begins to function or be recognized as a symbolic representation or emblem of another entity.
-
E.
inceptionPurpose
Indicates the intended purpose, goal, or function for which something was originally created, initiated, or established.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:19 p.m.