Triple
T36625266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelly Crossing |
E904151
|
entity |
| Predicate | accessToHistoricSite |
P127077
|
FINISHED |
| Object | Fort Selkirk by riverboat |
—
|
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: Fort Selkirk by riverboat | Statement: [Pelly Crossing, accessToHistoricSite, Fort Selkirk by riverboat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToHistoricSite Context triple: [Pelly Crossing, accessToHistoricSite, Fort Selkirk by riverboat]
-
A.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
B.
servesHistoricSites
chosen
Indicates that an entity provides services, access, or support specifically to historic sites.
-
C.
heritageAttraction
Indicates that something is recognized or designated as a heritage-related attraction, typically of cultural, historical, or natural significance.
-
D.
memorialSiteAccess
Indicates that an entity has the right, ability, or permission to enter or use a memorial site.
-
E.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.