Triple
T25483794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of London (1871) |
E638644
|
entity |
| Predicate | placeInChronology |
P10630
|
FINISHED |
| Object | after Franco-Prussian War armistice |
—
|
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: after Franco-Prussian War armistice | Statement: [Treaty of London (1871), placeInChronology, after Franco-Prussian War armistice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInChronology Context triple: [Treaty of London (1871), placeInChronology, after Franco-Prussian War armistice]
-
A.
chronologicalPosition
chosen
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
chronologicalPoint
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
C.
chronologicallySetIn
Indicates that one event, scene, or narrative is situated at a specific point or period in time relative to a broader temporal context.
-
D.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
E.
chronologyIn
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 2:31 p.m.