Triple
T26628157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giovanni Battista Rezzonico |
E668414
|
entity |
| Predicate | familyAchievedProminenceIn |
P166157
|
FINISHED |
| Object | Rome |
—
|
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: Rome | Statement: [Giovanni Battista Rezzonico, familyAchievedProminenceIn, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyAchievedProminenceIn Context triple: [Giovanni Battista Rezzonico, familyAchievedProminenceIn, Rome]
-
A.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
B.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
C.
familyNotableRole
Indicates that a member of the family holds or held a particularly significant, distinguished, or influential role.
-
D.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
E.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 2:23 a.m.