Triple
T1585928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Monroe, Virginia |
E34064
|
entity |
| Predicate | closedAsArmyPost |
P16659
|
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, Virginia, closedAsArmyPost, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedAsArmyPost Context triple: [Fort Monroe, Virginia, closedAsArmyPost, 2011]
-
A.
closedAsActiveArmyPost
chosen
Indicates that a location or facility ceased operations specifically in its role as an active Army post.
-
B.
closedUnder
Indicates that applying a specified operation to elements within a set always produces a result that is also an element of that same set.
-
C.
closed
Indicates that an entity has brought something (such as an object, container, or space) from an open state into a shut or sealed state, or that it is currently in that shut state.
-
D.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another entity.
-
E.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.