Triple
T24145110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museo Nazionale Romano |
E598356
|
entity |
| Predicate | mainBuildingNear |
P44972
|
FINISHED |
| Object | Termini railway station |
—
|
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: Termini railway station | Statement: [Museo Nazionale Romano, mainBuildingNear, Termini railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBuildingNear Context triple: [Museo Nazionale Romano, mainBuildingNear, Termini railway station]
-
A.
hasMainBuildingNear
chosen
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
-
B.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
C.
mainBuildingName
Indicates the name that is designated as the primary or main building associated with an entity.
-
D.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
E.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00a37b881909e31f85a667e6d83 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:29 p.m.