Triple
T35172261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rione Parione |
E1015574
|
entity |
| Predicate | hasNotableFountain |
P204288
|
FINISHED |
| Object | Fontana dei Quattro Fiumi |
E92679
|
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: Fontana dei Quattro Fiumi | Statement: [Rione Parione, hasNotableFountain, Fontana dei Quattro Fiumi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFountain Context triple: [Rione Parione, hasNotableFountain, Fontana dei Quattro Fiumi]
-
A.
hasNotableWriter
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
-
B.
hasNotableRecognitionAs
Indicates that an entity has received notable recognition, distinction, or status specifically in the role, capacity, or identity denoted by the related entity.
-
C.
hasNotableFable
Indicates that an entity is associated with a well-known or significant fable, either as its subject, source, or key element.
-
D.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
-
E.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb138f3481909e39dd48e1187e9b |
completed | June 21, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
| PDg | Predicate description generation | batch_6a036b0678448190be865dd52792efab |
completed | May 12, 2026, 6:01 p.m. |
Created at: May 3, 2026, 4:02 p.m.