Triple
T34455937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota and Ontario |
E884502
|
entity |
| Predicate | hasSharedHistoricalUse |
P183763
|
FINISHED |
| Object | fur trade routes |
—
|
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 trade routes | Statement: [Minnesota and Ontario, hasSharedHistoricalUse, fur trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSharedHistoricalUse Context triple: [Minnesota and Ontario, hasSharedHistoricalUse, fur trade routes]
-
A.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
-
B.
hasPrimaryUseHistoric
Indicates that something is primarily used for historic or heritage-related purposes.
-
C.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
D.
hasHistoricalService
Indicates that an entity has previously provided service or fulfilled a role during a past historical period or event.
-
E.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
- F. None of above. chosen
Provenance (4 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 1, 2026, 2 a.m.