Triple
T34799533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian general election, 1913 |
E1003178
|
entity |
| Predicate | leader5 |
P182878
|
FINISHED |
| Object | Luigi Federzoni |
—
|
NE NERFINISHED |
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: Luigi Federzoni | Statement: [Italian general election, 1913, leader5, Luigi Federzoni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader5 Context triple: [Italian general election, 1913, leader5, Luigi Federzoni]
-
A.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
B.
leaderType
Indicates the specific role or category of leadership that an entity holds within an organization, group, or context.
-
C.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
D.
leaderClass
Indicates that one entity serves as the primary leader or head within a specified class, group, or category of entities.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 3:59 p.m.