Triple
T470740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Sumter |
E8548
|
entity |
| Predicate | firstShotsFiredAt |
P13395
|
FINISHED |
| Object | Union garrison |
—
|
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: Union garrison | Statement: [Fort Sumter, firstShotsFiredAt, Union garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstShotsFiredAt Context triple: [Fort Sumter, firstShotsFiredAt, Union garrison]
-
A.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
C.
firstSuccessfulImpactBy
Indicates that one entity is the earliest or initial successful impactor upon another entity in a given context or sequence of events.
-
D.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
E.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
- 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.