Triple
T37553778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackrock Depths |
E933645
|
entity |
| Predicate | travelAccessPoint |
P17407
|
FINISHED |
| Object | Blackrock Mountain central chamber |
—
|
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: Blackrock Mountain central chamber | Statement: [Blackrock Depths, travelAccessPoint, Blackrock Mountain central chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelAccessPoint Context triple: [Blackrock Depths, travelAccessPoint, Blackrock Mountain central chamber]
-
A.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
-
B.
cityAccess
Indicates that an entity has permission or the ability to enter, use, or reach a particular city.
-
C.
tourStaple
Indicates that something is a standard, frequently included element or highlight of a tour.
-
D.
touristGatewayTo
chosen
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
-
E.
tourInformation
Indicates that an entity provides details or data about a tour, such as schedule, itinerary, or features.
- 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.