Triple
T5457379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Churchill |
E122512
|
entity |
| Predicate | stateHistoricParkEstablished |
P54654
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Fort Churchill, stateHistoricParkEstablished, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHistoricParkEstablished Context triple: [Fort Churchill, stateHistoricParkEstablished, 1930s]
-
A.
stateParkEstablishedFor
Indicates that a state park was created or designated for the benefit, use, or purpose of a particular entity or objective.
-
B.
dateEstablishedAsNationalPark
Indicates the date on which a location or area was officially designated as a national park.
-
C.
hasNationalHistoricalPark
Indicates that an entity possesses or is associated with a designated National Historical Park.
-
D.
establishedAsPark
chosen
Indicates that an area or site has been officially designated and recognized as a park.
-
E.
establishedAsNationalParkBy
Indicates that an area or site was officially designated and created as a national park through the action or authority of a specific person, organization, or governmental body.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.