Triple
T32183698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natchez War |
E822049
|
entity |
| Predicate | hasAllyOfFrench |
P146243
|
FINISHED |
| Object | Choctaw |
—
|
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: Choctaw | Statement: [Natchez War, hasAllyOfFrench, Choctaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllyOfFrench Context triple: [Natchez War, hasAllyOfFrench, Choctaw]
-
A.
usedByFrance
Indicates that something is utilized, employed, or operated by France as a country or its official institutions.
-
B.
joinedFrance
Indicates that an entity became a member of or was incorporated into France.
-
C.
FrenchOutcome
Indicates that an event, action, or process results in an outcome that is specifically French in nature, context, or origin.
-
D.
vassalOrAllyOf
chosen
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
-
E.
FrenchRole
Indicates a role or position that an entity holds specifically within a French context (e.g., in France or related to French institutions, culture, or language).
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 12:34 a.m.