Triple
T21071757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arte di Calimala |
E519123
|
entity |
| Predicate | hadPoliticalPower |
P105079
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Arte di Calimala, hadPoliticalPower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPoliticalPower Context triple: [Arte di Calimala, hadPoliticalPower, yes]
-
A.
hasPoliticalPower
chosen
Indicates that one entity holds authority or influence to make, shape, or enforce political decisions over another entity or within a political system.
-
B.
hadExecutivePowerIn
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
-
C.
heldPoliticalOfficeIn
Indicates that an entity served in a political office or position within a specified governmental body or jurisdiction.
-
D.
hadMonopolyOnPower
Indicates that one entity exclusively controlled or dominated power or authority, without significant competition or sharing with others.
-
E.
exercisedPowerAs
Indicates that one entity actively used or wielded authority, influence, or control in the capacity or role specified by another entity.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:46 p.m.