Triple
T28334997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Wetherill |
E717645
|
entity |
| Predicate | abandonedByMilitary |
P164414
|
FINISHED |
| Object | mid-20th 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: mid-20th century | Statement: [Fort Wetherill, abandonedByMilitary, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedByMilitary Context triple: [Fort Wetherill, abandonedByMilitary, mid-20th century]
-
A.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
B.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
C.
abandonedAsFort
Indicates that a location or structure previously used as a fort has been given up and is no longer maintained or occupied for defensive or military purposes.
-
D.
formerMilitaryBase
Indicates that a location was previously used as a military base but no longer serves that function.
-
E.
abandonedAsPermanentSettlement
Indicates that a place or site has been given up and is no longer used as a permanent settlement.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5645d48190b0c3a2bad5a2e539 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 12:35 a.m.