Triple
T31690352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gap Cave |
E808772
|
entity |
| Predicate | tourAccessPoint |
P79603
|
FINISHED |
| Object | Cumberland Gap National Historical Park visitor center |
—
|
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: Cumberland Gap National Historical Park visitor center | Statement: [Gap Cave, tourAccessPoint, Cumberland Gap National Historical Park visitor center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourAccessPoint Context triple: [Gap Cave, tourAccessPoint, Cumberland Gap National Historical Park visitor center]
-
A.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
-
B.
visitorAccessPoint
chosen
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
C.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
D.
tourStopOf
Indicates that one entity is a stop or scheduled visit location within the itinerary or route of another entity’s tour.
-
E.
tourArea
Indicates that an entity conducts, offers, or is associated with tours within a specified geographic area or region.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:08 p.m.