Triple
T22286038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Monroe National Monument |
E550862
|
entity |
| Predicate | decommissionedAsArmyPost |
P14100
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Fort Monroe National Monument, decommissionedAsArmyPost, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissionedAsArmyPost Context triple: [Fort Monroe National Monument, decommissionedAsArmyPost, 2011]
-
A.
establishedAsArmyPost
Indicates that a location or site was formally designated and set up to function as a military post or army installation.
-
B.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
C.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified entity.
-
D.
closedAsActiveArmyPost
Indicates that a location or facility ceased operations specifically in its role as an active Army post.
-
E.
decommissionedDate
chosen
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15607d9948190b4b8e9cd7fa4d390 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.