Triple
T28459922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French River Provincial Park |
E720121
|
entity |
| Predicate | wasHistoricRouteFor |
P12633
|
FINISHED |
| Object | fur traders |
—
|
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: fur traders | Statement: [French River Provincial Park, wasHistoricRouteFor, fur traders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasHistoricRouteFor Context triple: [French River Provincial Park, wasHistoricRouteFor, fur traders]
-
A.
historicalRouteVia
Indicates that a historical route or path passed through or was connected by a particular intermediate location or segment.
-
B.
hasHistoricalRoute
chosen
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
-
C.
historicalRouteName
Indicates that an entity has or is associated with a name it held historically as a route or pathway, distinct from its current official name.
-
D.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
E.
nearHistoricalRoute
Indicates that one entity is located close to a historically significant route or pathway.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64ea4d644819092d142a5f62f643c |
completed | May 2, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:38 a.m.