Triple
T25867945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazza Salimbeni |
E651669
|
entity |
| Predicate | statueSubject |
P174658
|
FINISHED |
| Object | Sallustio Bandini |
E1699279
|
NE 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: Sallustio Bandini | Statement: [Piazza Salimbeni, statueSubject, Sallustio Bandini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statueSubject Context triple: [Piazza Salimbeni, statueSubject, Sallustio Bandini]
-
A.
statueSubjectRequirement
Indicates that a statue must depict or be associated with a specific required subject or type of subject.
-
B.
statueName
Indicates that a statue has a specific name or title associated with it.
-
C.
topStatue
Indicates that one entity is positioned as a statue on top of another entity.
-
D.
statuesBy
Indicates that one entity is the creator, sculptor, or originator of statues depicting or associated with another entity.
-
E.
monumentSubject
Indicates that the subject serves as the monument or commemorative structure associated with another entity.
- F. None of above. chosen
Provenance (5 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ecb22dec8190bbc3eff54c86d743 |
completed | May 22, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 22, 2026, 8:07 a.m.