Triple
T9842545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Procuratie Vecchie |
E239261
|
entity |
| Predicate | positionOnSquare |
P66689
|
FINISHED |
| Object | north side of Piazza San Marco |
—
|
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: north side of Piazza San Marco | Statement: [Procuratie Vecchie, positionOnSquare, north side of Piazza San Marco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnSquare Context triple: [Procuratie Vecchie, positionOnSquare, north side of Piazza San Marco]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionInNotation
Indicates the specific place or index that an element occupies within a given ordered notation or representation.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
-
E.
locationOnSquare
chosen
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34e3420819084bb31170e643cd0 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.