Triple
T1350997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Tahoe Airport |
E28880
|
entity |
| Predicate | hasNoScheduledCommercialService |
P3875
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Tahoe Airport, hasNoScheduledCommercialService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoScheduledCommercialService Context triple: [Lake Tahoe Airport, hasNoScheduledCommercialService, true]
-
A.
usedForTelevisionBroadcastSchedules
Indicates that something is utilized to organize, present, or manage the timing and content of television broadcast schedules.
-
B.
doesNotServe
chosen
Indicates that one entity explicitly does not provide a service, function, or role to another entity.
-
C.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
D.
hasBroadcastCoverageIn
Indicates that a broadcast (such as a TV or radio program, channel, or signal) is available or transmitted within a specified geographic area or region.
-
E.
isUsedInTransportTimetables
Indicates that something is employed or referenced within transport timetables or schedules.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.