Triple
T31970588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloody Creek |
E816300
|
entity |
| Predicate | eraOfKeyEvents |
P145541
|
FINISHED |
| Object | early 18th century |
—
|
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 18th century | Statement: [Bloody Creek, eraOfKeyEvents, early 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfKeyEvents Context triple: [Bloody Creek, eraOfKeyEvents, early 18th century]
-
A.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
historicalEventsDescribed
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
D.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
E.
notableEventPeriod
chosen
Indicates the time span during which a notable or significant event associated with an entity took place.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:10 a.m.