Triple
T27802969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champion family plantation |
E702294
|
entity |
| Predicate | stateDuringCivilWar |
P86860
|
FINISHED |
| Object | Confederate States of America |
—
|
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: Confederate States of America | Statement: [Champion family plantation, stateDuringCivilWar, Confederate States of America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateDuringCivilWar Context triple: [Champion family plantation, stateDuringCivilWar, Confederate States of America]
-
A.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
B.
stateDuringWar
chosen
Indicates that a state or condition exists specifically in the context of, or for the duration of, a war or armed conflict.
-
C.
civilWarTheater
Indicates a geographic or operational area where events of a civil war take place or are focused.
-
D.
hasCivilWarAssociation
Indicates a relationship in which an entity is connected or related to a civil war, such as through involvement, impact, or relevance.
-
E.
stateEnteredByConfederates
Indicates that a particular state or region was entered or invaded by Confederate forces.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 5:36 p.m.