Triple
T35555080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pietro Aldobrandini |
E1027470
|
entity |
| Predicate | roleInConclaves |
P203293
|
FINISHED |
| Object | leader of the Clementine faction |
—
|
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: leader of the Clementine faction | Statement: [Pietro Aldobrandini, roleInConclaves, leader of the Clementine faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInConclaves Context triple: [Pietro Aldobrandini, roleInConclaves, leader of the Clementine faction]
-
A.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
B.
roleInCons
Indicates that an entity holds a specific role or function within a particular consortium.
-
C.
consensusRole
Indicates that an entity participates in a consensus process with a specific functional role (e.g., proposer, validator, leader, or follower) within that agreement mechanism.
-
D.
chamberRole
Indicates the specific function, position, or capacity an entity holds within a legislative or deliberative chamber.
-
E.
rankInCouncil
Indicates the relative position or level of authority an entity holds within a council or governing body.
- 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a014a0b57dc8190b04ce51156ab95fa |
completed | May 11, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0149afa57c8190a83257085766d916 |
completed | May 11, 2026, 3:14 a.m. |
| PDg | Predicate description generation | batch_6a014a0ab56c819082ce383fb5987654 |
completed | May 11, 2026, 3:16 a.m. |
Created at: May 3, 2026, 4:04 p.m.