Triple
T14562636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medieval walls of Viterbo |
E341704
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Porta Romana |
E454717
|
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: Porta Romana | Statement: [medieval walls of Viterbo, hasPart, Porta Romana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Porta Romana Context triple: [medieval walls of Viterbo, hasPart, Porta Romana]
-
A.
Porta Romana
Porta Romana is a historic city gate in Velletri, Italy, notable as one of the traditional entrances to the town.
-
B.
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.
-
C.
Porta Romana
Porta Romana is a historic town gate in Valentano, Italy, notable as one of the main entrances to its old medieval center.
-
D.
Porta Romana
chosen
Porta Romana is a historic city gate in Viterbo, Italy, serving as one of the traditional entrances through the town’s medieval walls.
-
E.
Porta Romana
Porta Romana is a historic city gate in Norcia, Italy, notable as one of the main entrances through the town’s medieval walls.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38afa8881909c9151b7620949ae |
completed | April 14, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd94b4013881908fddb8b3cf8494de |
completed | May 8, 2026, 7:45 a.m. |
Created at: April 10, 2026, 1:23 a.m.