Triple
T16141680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauk and Fox |
E391671
|
entity |
| Predicate | hasHistoricalPeriodOfConflict |
P121264
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Sauk and Fox, hasHistoricalPeriodOfConflict, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPeriodOfConflict Context triple: [Sauk and Fox, hasHistoricalPeriodOfConflict, early 19th century]
-
A.
opponentInHistoricalConflict
Indicates that two entities stood on opposing sides in a specific historical conflict or war.
-
B.
partOfHistoricalConflict
Indicates that one entity participated in, belonged to, or was involved as a component of a larger historical conflict or war.
-
C.
hasMonthOfConflict
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
-
D.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
E.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a087c848190aba9ed2ccb422427 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.