Triple
T33990088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow airports |
E871517
|
entity |
| Predicate | connectedToCityCenter |
P97106
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Moscow airports, connectedToCityCenter, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToCityCenter Context triple: [Moscow airports, connectedToCityCenter, rail]
-
A.
connectsToUrbanCenter
chosen
Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
-
B.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
C.
connectedToPlace
Indicates that one entity has a spatial, functional, or relational link or association with a specific place.
-
D.
cityCentreAccess
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
E.
hasCoordinateInCityCentreApprox
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 1:50 a.m.