Triple
T3320159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camillo Benso, Count of Cavour |
E69774
|
entity |
| Predicate | keyFigureIn |
P256
|
FINISHED |
| Object | Italian unification |
—
|
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: Italian unification | Statement: [Camillo Benso, Count of Cavour, keyFigureIn, Italian unification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyFigureIn Context triple: [Camillo Benso, Count of Cavour, keyFigureIn, Italian unification]
-
A.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
B.
keyPerson
chosen
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
C.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
D.
keyMember
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
E.
keyFigureInDebate
Indicates that an entity plays a central, influential, or prominently recognized role in a particular debate or controversy.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13a4e948190841134d6ae6ef432 |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.