Triple
T407399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Paris (1763) |
E9412
|
entity |
| Predicate | concludedOn |
P2818
|
FINISHED |
| Object | 1763-02-10 |
—
|
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: 1763-02-10 | Statement: [Treaty of Paris (1763), concludedOn, 1763-02-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludedOn Context triple: [Treaty of Paris (1763), concludedOn, 1763-02-10]
-
A.
concludedAt
chosen
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
B.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
C.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
D.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
E.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbd766c8190bb8a91605929156a |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.