Triple
T501883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fascist Italy |
E10418
|
entity |
| Predicate | yearOfLateranTreaty |
P2503
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Fascist Italy, yearOfLateranTreaty, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfLateranTreaty Context triple: [Fascist Italy, yearOfLateranTreaty, 1929]
-
A.
papalBull
Indicates that a formal decree, charter, or proclamation has been issued by the Pope regarding the related entity or matter.
-
B.
treatyDate
chosen
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
C.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
D.
treatyEnteredIntoForce
Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
-
E.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.