Triple
T643540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson's Bay Company |
E16791
|
entity |
| Predicate | heldMonopolyOn |
P2908
|
FINISHED |
| Object | fur trade in Rupert's Land |
—
|
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 in Rupert's Land | Statement: [Hudson's Bay Company, heldMonopolyOn, fur trade in Rupert's Land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldMonopolyOn Context triple: [Hudson's Bay Company, heldMonopolyOn, fur trade in Rupert's Land]
-
A.
monopolyOn
chosen
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
B.
monopolyRestricted
Indicates that an entity’s monopoly power or exclusive control over a market, resource, or service is limited, regulated, or otherwise constrained.
-
C.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
D.
heldThat
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
-
E.
heldRight
Indicates that one entity is being held on the right side of another entity.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f18216081908331aa12dac40214 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.