Triple
T24004005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neri di Fioravante |
E594321
|
entity |
| Predicate | notableWorkLocationType |
P133323
|
FINISHED |
| Object | civic buildings |
—
|
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: civic buildings | Statement: [Neri di Fioravante, notableWorkLocationType, civic buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkLocationType Context triple: [Neri di Fioravante, notableWorkLocationType, civic buildings]
-
A.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
-
B.
commissionedWorkLocation
Indicates the place where a commissioned work is created, produced, or carried out.
-
C.
venueOfNotableWork
chosen
Indicates the place or location where a notable work was created, performed, exhibited, or otherwise prominently presented.
-
D.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
-
E.
notableRoleLocation
Indicates that an entity’s notable role, position, or function is specifically associated with a particular geographic location.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d467108481909e33de1c7319738a |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.