Triple
T1429162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Paris (1856) |
E30403
|
entity |
| Predicate | treatySubject |
P23331
|
FINISHED |
| Object | Crimean War settlement |
—
|
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: Crimean War settlement | Statement: [Treaty of Paris (1856), treatySubject, Crimean War settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySubject Context triple: [Treaty of Paris (1856), treatySubject, Crimean War settlement]
-
A.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
B.
treatyType
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
-
C.
treatyName
Indicates the formal name or title assigned to a specific treaty.
-
D.
treatyScope
chosen
Indicates the range, subject matter, or extent of issues and obligations that a treaty covers or applies to.
-
E.
treatyOrLegalIssue
Indicates a formal agreement, dispute, or matter governed by treaties or legal frameworks between parties.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.