Triple
T470748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Sumter |
E8548
|
entity |
| Predicate | reoccupiedByUnionForces |
P13396
|
FINISHED |
| Object | 1865 |
—
|
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: 1865 | Statement: [Fort Sumter, reoccupiedByUnionForces, 1865]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reoccupiedByUnionForces Context triple: [Fort Sumter, reoccupiedByUnionForces, 1865]
-
A.
occupyingPower
Indicates that one entity holds military or political control over a territory that it does not legally own, typically as an occupying authority.
-
B.
reoccupiedAsGovernorResidenceUntil
Indicates that an individual resumed using a residence in their capacity as governor and continued to occupy it in that role until a specified time.
-
C.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
-
D.
civilWarEnd
Indicates that an internal armed conflict within a country has come to an official or de facto conclusion.
-
E.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.