Triple
T26277760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Gatwick – Rio de Janeiro |
E660620
|
entity |
| Predicate | linkedCityRegion |
P174333
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [London Gatwick – Rio de Janeiro, linkedCityRegion, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedCityRegion Context triple: [London Gatwick – Rio de Janeiro, linkedCityRegion, London]
-
A.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
B.
terminalCityRegion
Indicates that a city serves as the terminal (end-point) location within a specified region for a route, line, or connection.
-
C.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
D.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
-
E.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
- F. None of above. chosen
Provenance (4 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 26, 2026, 9:57 p.m.