Triple
T2658896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Glass |
E54678
|
entity |
| Predicate | hasLegendaryStatus |
P2007
|
FINISHED |
| Object | American frontier folklore |
—
|
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: American frontier folklore | Statement: [Hugh Glass, hasLegendaryStatus, American frontier folklore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryStatus Context triple: [Hugh Glass, hasLegendaryStatus, American frontier folklore]
-
A.
hasIconicStatus
chosen
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
-
B.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
C.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
D.
hallOfFameEligibility
Indicates whether an entity meets the criteria or conditions required to be considered for induction into a hall of fame.
-
E.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94dcaa48190aec625f68ce61a02 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.