Triple
T2542534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Wars |
E57816
|
entity |
| Predicate | earliestConflictApproximateStart |
P22233
|
FINISHED |
| Object | late 18th 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: late 18th century | Statement: [Frontier Wars, earliestConflictApproximateStart, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestConflictApproximateStart Context triple: [Frontier Wars, earliestConflictApproximateStart, late 18th century]
-
A.
conflictStartTime
chosen
Indicates the specific point in time at which a conflict between entities begins.
-
B.
yearOfFirstBattle
Indicates the specific year in which the first battle involving the given entities took place.
-
C.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
D.
chronologyWithinConflict
Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
-
E.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bd92f88190bf100c799f62210c |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.