Triple
T6178177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fontana del Moro |
E137872
|
entity |
| Predicate | positionInSquare |
P66689
|
FINISHED |
| Object | southern end of Piazza Navona |
—
|
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: southern end of Piazza Navona | Statement: [Fontana del Moro, positionInSquare, southern end of Piazza Navona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSquare Context triple: [Fontana del Moro, positionInSquare, southern end of Piazza Navona]
-
A.
positionInNotation
Indicates the specific place or index that an element occupies within a given ordered notation or representation.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
locationOnSquare
chosen
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
D.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc9f3d88190ab46b3b246f5a8df |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.