Triple
T9047105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Democracy (Italy) |
E216779
|
entity |
| Predicate | roleInConstituentAssembly |
P4024
|
FINISHED |
| Object | largest party |
—
|
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: largest party | Statement: [Christian Democracy (Italy), roleInConstituentAssembly, largest party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInConstituentAssembly Context triple: [Christian Democracy (Italy), roleInConstituentAssembly, largest party]
-
A.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
-
B.
parliamentaryRoleIn
Indicates that an entity holds or has held a specific role, position, or function within a particular parliament or parliamentary body.
-
C.
legislativeRole
chosen
Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
-
D.
parliamentEntry
Indicates that an entity assumes or is granted membership or a seat in a parliamentary body.
-
E.
representedInNationalAssembly
Indicates that an entity has official representation or a seat in a country's national legislative assembly.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b5022c88190ab6b6de3c3830a41 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.