Triple
T29038318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells, British Columbia |
E737925
|
entity |
| Predicate | nearestHistoricSite |
P87975
|
FINISHED |
| Object | Barkerville Historic Town |
—
|
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: Barkerville Historic Town | Statement: [Wells, British Columbia, nearestHistoricSite, Barkerville Historic Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestHistoricSite Context triple: [Wells, British Columbia, nearestHistoricSite, Barkerville Historic Town]
-
A.
nearbyRoyalSite
Indicates that one place or object is located close to a site associated with royalty, such as a palace, castle, or royal residence.
-
B.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
C.
hasAdjacentHistoricSite
chosen
Indicates that one place is directly next to or very near another place that is recognized as a historic site.
-
D.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
E.
nearbyProtectedSite
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 10 a.m.