Triple
T8925421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porta del Popolo |
E212528
|
entity |
| Predicate | directionOfEntrance |
P1974
|
FINISHED |
| Object | northern entrance to Rome |
—
|
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: northern entrance to Rome | Statement: [Porta del Popolo, directionOfEntrance, northern entrance to Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfEntrance Context triple: [Porta del Popolo, directionOfEntrance, northern entrance to Rome]
-
A.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
B.
hasEntranceOn
chosen
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
entranceSize
Indicates the size or dimensions of an entrance relative to a referenced object or structure.
-
E.
entranceWidth
Indicates the measured horizontal span of an entrance opening that defines how wide the entry passage is.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66700fb48190874563e535f20437 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.