Triple
T25125642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pleso Airport |
E629386
|
entity |
| Predicate | distanceFromCityCenter_direction |
P59958
|
FINISHED |
| Object | southeast |
—
|
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: southeast | Statement: [Pleso Airport, distanceFromCityCenter_direction, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCityCenter_direction Context triple: [Pleso Airport, distanceFromCityCenter_direction, southeast]
-
A.
distanceFromCityCenterDirection
chosen
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
B.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
C.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
D.
directionWithinCity
Indicates a directional relationship specifying where something is located or oriented within the boundaries of a particular city.
-
E.
directionFromParkCenter
Indicates the compass direction or relative bearing of an entity when measured outward from the center point of a park.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 18, 2026, 6:28 a.m.