Triple
T28731950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbiad |
E730682
|
entity |
| Predicate | hasNotableEngagement |
P1700
|
FINISHED |
| Object | siege of Fort Sumter |
—
|
NE NERFINISHED |
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: siege of Fort Sumter | Statement: [Columbiad, hasNotableEngagement, siege of Fort Sumter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEngagement Context triple: [Columbiad, hasNotableEngagement, siege of Fort Sumter]
-
A.
notableEngagement
chosen
Indicates a significant interaction, involvement, or participation between entities that is noteworthy or distinguished in some context.
-
B.
hasSocialEngagement
Indicates that an entity participates in or maintains some form of social interaction, activity, or relationship with others.
-
C.
hasNotableResponse
Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
-
D.
hasNotableNumber
Indicates that an entity is associated with a specific number that is considered significant, distinctive, or noteworthy in some context.
-
E.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: April 28, 2026, 5:58 a.m.