Triple
T22186751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museo delle Mura |
E548314
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Porta Latina |
—
|
NE NERFINISHED |
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: Porta Latina | Statement: [Museo delle Mura, near, Porta Latina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Porta Latina Context triple: [Museo delle Mura, near, Porta Latina]
-
A.
Porta Latina
chosen
Porta Latina is an ancient gate in the Aurelian Walls of Rome, historically serving as one of the southern entrances to the city.
-
B.
Porta Romana
Porta Romana is a historic city gate in Velletri, Italy, notable as one of the traditional entrances to the town.
-
C.
Porta Romana
Porta Romana is a historic city gate of Terra del Sole in Italy, notable as one of the main fortified entrances to the Renaissance-planned town.
-
D.
Porta Romana
Porta Romana is a historic town gate in Valentano, Italy, notable as one of the main entrances to its old medieval center.
-
E.
Porta Romana
Porta Romana is a historic city gate and surrounding district in Milan, Italy, known for its architectural heritage and vibrant urban life.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa8f178819094d1556df5aee5b9 |
completed | April 28, 2026, 9:46 p.m. |
Created at: April 16, 2026, 8:35 p.m.