Triple
T37552119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highmountain |
E933611
|
entity |
| Predicate | hasFlightPathNetwork |
P72756
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Highmountain, hasFlightPathNetwork, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightPathNetwork Context triple: [Highmountain, hasFlightPathNetwork, yes]
-
A.
hasAirTravelLink
Indicates that there is a direct or established air travel connection (such as flights or air routes) between the related entities.
-
B.
flightRoute
Indicates a path or sequence of locations that a particular flight travels between, typically from its origin to its destination (and possibly via intermediate stops).
-
C.
hasRouteNetwork
chosen
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
D.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
-
E.
hasCityPair
Indicates a relationship that links two cities considered as a connected or associated pair, often for purposes such as travel, trade, or comparison.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.