Triple
T24669462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airport Direct |
E610783
|
entity |
| Predicate | destinationArea |
P10883
|
FINISHED |
| Object | Reykjavík and surroundings |
—
|
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: Reykjavík and surroundings | Statement: [Airport Direct, destinationArea, Reykjavík and surroundings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationArea Context triple: [Airport Direct, destinationArea, Reykjavík and surroundings]
-
A.
territoryOfDestination
Indicates that a specified territory is the destination or endpoint location associated with an action, movement, or relation.
-
B.
targetArea
chosen
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
C.
destinationCouncilArea
Indicates the council or local government area that serves as the destination location in a movement, transfer, or travel relationship.
-
D.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
E.
venueArea
Indicates the physical size or spatial extent of a venue, typically measured in units such as square meters or square feet.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:42 a.m.