Triple
T36790664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rock of Chickamauga |
E909043
|
entity |
| Predicate | earnedDuringConflict |
P186554
|
FINISHED |
| Object | American Civil War |
—
|
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: American Civil War | Statement: [The Rock of Chickamauga, earnedDuringConflict, American Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedDuringConflict Context triple: [The Rock of Chickamauga, earnedDuringConflict, American Civil War]
-
A.
heldDuringConflict
Indicates that an entity maintained control, possession, or occupation of something for some duration while an identified conflict was ongoing.
-
B.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
C.
builtDuringConflict
Indicates that the construction of one entity occurred while a specified conflict or war was taking place.
-
D.
significantDuringConflict
Indicates that something plays an important or influential role specifically in the context of a conflict or dispute.
-
E.
reignDuringConflict
Indicates that a ruler’s period of reign overlaps in time with a specified conflict or war.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.