Triple
T38682190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Renaissance |
E943916
|
entity |
| Predicate | hasPatronageSystem |
P133420
|
FINISHED |
| Object | Medici family |
—
|
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: Medici family | Statement: [Early Renaissance, hasPatronageSystem, Medici family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronageSystem Context triple: [Early Renaissance, hasPatronageSystem, Medici family]
-
A.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
B.
hasImperialPatronage
Indicates that an entity receives official support, sponsorship, or protection from an imperial authority.
-
C.
patronageStyle
Indicates the manner or characteristic way in which support, sponsorship, or patronage is provided in a relationship.
-
D.
patronage
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
-
E.
hasPatronageContext
chosen
Indicates that one entity is involved with or characterized by a particular patronage relationship, setting, or circumstances.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.