Triple
T7865811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortress Monroe |
E182610
|
entity |
| Predicate | statusDuringAmericanCivilWar |
P19322
|
FINISHED |
| Object | remained under Union control |
—
|
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: remained under Union control | Statement: [Fortress Monroe, statusDuringAmericanCivilWar, remained under Union control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringAmericanCivilWar Context triple: [Fortress Monroe, statusDuringAmericanCivilWar, remained under Union control]
-
A.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
B.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
C.
stateEnteredByConfederates
Indicates that a particular state or region was entered or invaded by Confederate forces.
-
D.
civilWarEnd
Indicates that an internal armed conflict within a country has come to an official or de facto conclusion.
-
E.
positionWithinConfederacy
Indicates that one entity holds a specific role, rank, or status within a confederated group or alliance of entities.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3844eacc81908f8e1e5fc4dafec8 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:54 p.m.