Triple
T17769155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlusconi I Cabinet |
E443586
|
entity |
| Predicate | includedPartyFrom |
P98307
|
FINISHED |
| Object | post-Christian Democratic area |
—
|
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: post-Christian Democratic area | Statement: [Berlusconi I Cabinet, includedPartyFrom, post-Christian Democratic area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPartyFrom Context triple: [Berlusconi I Cabinet, includedPartyFrom, post-Christian Democratic area]
-
A.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
B.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
C.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
D.
componentParty
chosen
Indicates that one party functions as a constituent or member of a larger party or group within a composite relationship.
-
E.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fe70648190b4107e1eabacc694 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.