Triple
T1012110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Turin (1860) |
E21845
|
entity |
| Predicate | voteOutcomeInNice |
P10095
|
FINISHED |
| Object | majority in favor of union with France |
—
|
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: majority in favor of union with France | Statement: [Treaty of Turin (1860), voteOutcomeInNice, majority in favor of union with France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteOutcomeInNice Context triple: [Treaty of Turin (1860), voteOutcomeInNice, majority in favor of union with France]
-
A.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
B.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
C.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
D.
voteSplit
Indicates that a voting outcome is divided among multiple options or parties rather than being unanimous or clearly majority.
-
E.
vote
Indicates that an entity formally expresses a choice or preference in a decision-making process, typically an election or poll.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.