Triple
T11639447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Classic |
E276620
|
entity |
| Predicate | offersConnections |
P8172
|
FINISHED |
| Object | Kenai Fjords National Park tours |
—
|
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: Kenai Fjords National Park tours | Statement: [Coastal Classic, offersConnections, Kenai Fjords National Park tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersConnections Context triple: [Coastal Classic, offersConnections, Kenai Fjords National Park tours]
-
A.
offersConnectionTo
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
B.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
C.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
D.
offersMarket
Indicates that one entity provides or makes available a market (as a venue or opportunity for buying, selling, or trading) to another entity.
-
E.
offersServiceTo
chosen
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.