Triple
T29261363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eilat Airport |
E741853
|
entity |
| Predicate | servedDomesticDestination |
P195389
|
FINISHED |
| Object | Tel Aviv |
—
|
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: Tel Aviv | Statement: [Eilat Airport, servedDomesticDestination, Tel Aviv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedDomesticDestination Context triple: [Eilat Airport, servedDomesticDestination, Tel Aviv]
-
A.
primaryDomesticDestination
Indicates that one location is the main or most significant destination within the same country for travel, transport, or activity originating from another location.
-
B.
servedDestination
Indicates that a service or action is directed toward, or provided to, a particular destination.
-
C.
hasDomesticTerminal
Indicates that a transportation facility, typically an airport, includes a terminal dedicated to domestic (within-country) travel operations.
-
D.
isDomesticRouteIn
Indicates that a transportation route operates entirely within the boundaries of a specified country or internal region.
-
E.
destinationCountryServed
Indicates that a given entity (such as a service, route, or provider) serves or operates to a specified destination country.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: April 28, 2026, 12:41 p.m.