Triple
T21071754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arte di Calimala |
E519123
|
entity |
| Predicate | rankWithinFlorentineGuildSystem |
P142734
|
FINISHED |
| Object | major guild |
—
|
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: major guild | Statement: [Arte di Calimala, rankWithinFlorentineGuildSystem, major guild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinFlorentineGuildSystem Context triple: [Arte di Calimala, rankWithinFlorentineGuildSystem, major guild]
-
A.
nobleRankRequired
Indicates that a certain minimum noble rank or title is required for the related action, status, or relationship to apply.
-
B.
rankInPapalOrders
Indicates the relative hierarchical position or level an entity holds within the structure of papal orders.
-
C.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
D.
associatedWithNobleOrder
Indicates that an entity has a formal or recognized connection to a noble order, such as membership, affiliation, or honorary association.
-
E.
rankInCollegeOfCardinals
Indicates the specific hierarchical position a cardinal holds within the College of Cardinals.
- 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_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. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:46 p.m.