Triple
T11996515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mountain Fur Company |
E285543
|
entity |
| Predicate | notableEmployeeType |
P7128
|
FINISHED |
| Object | mountain men |
—
|
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: mountain men | Statement: [Rocky Mountain Fur Company, notableEmployeeType, mountain men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEmployeeType Context triple: [Rocky Mountain Fur Company, notableEmployeeType, mountain men]
-
A.
notablePersonnel
chosen
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
B.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
C.
notableSpeakerType
Indicates the type or category of a person who is recognized as a notable or distinguished speaker in a given context.
-
D.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
E.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c172788190b92042e9d10a48bf |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.