Triple
T447150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Paris (1783) |
E7046
|
entity |
| Predicate | exchangeOfRatificationsDate |
P1036
|
FINISHED |
| Object | 1784-05-12 |
—
|
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: 1784-05-12 | Statement: [Treaty of Paris (1783), exchangeOfRatificationsDate, 1784-05-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeOfRatificationsDate Context triple: [Treaty of Paris (1783), exchangeOfRatificationsDate, 1784-05-12]
-
A.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
B.
ratifiedOn
chosen
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
-
C.
treatyEnteredIntoForce
Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
-
D.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
E.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.