Triple
T1252457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch of Titus |
E26906
|
entity |
| Predicate | nearby |
P350
|
FINISHED |
| Object | Via Sacra |
E42847
|
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: Via Sacra | Statement: [Arch of Titus, nearby, Via Sacra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Via Sacra Context triple: [Arch of Titus, nearby, Via Sacra]
-
A.
Via Sacra
chosen
Via Sacra was the main ceremonial street of ancient Rome, running through the Roman Forum and used for triumphal processions and public religious events.
-
B.
Via Ostiense
Via Ostiense is a historic road in Rome that connects the city center to the Basilica of Saint Paul Outside the Walls and the ancient port of Ostia.
-
C.
Via Salaria
Via Salaria is an ancient Roman road that historically connected Rome to the Adriatic Sea, serving as a major route for the transport of salt and other goods.
-
D.
Via Appia
Via Appia is one of the earliest and most important ancient Roman roads, historically serving as a major route connecting Rome to southern Italy.
-
E.
Via Aurelia
Via Aurelia was an important ancient Roman road that ran along the Tyrrhenian coast of Italy, connecting Rome with key cities in Etruria and beyond.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf875cf48190b6781d41097ee39b |
completed | March 1, 2026, 10:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acb2fa8aec8190ad68b9dc87c85cfc |
completed | March 7, 2026, 11:21 p.m. |
Created at: March 1, 2026, 7:47 p.m.