Triple
T31071087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Restless Gun |
E791817
|
entity |
| Predicate | hasHeroArchetype |
P102015
|
FINISHED |
| Object | drifting gunfighter |
—
|
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: drifting gunfighter | Statement: [The Restless Gun, hasHeroArchetype, drifting gunfighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroArchetype Context triple: [The Restless Gun, hasHeroArchetype, drifting gunfighter]
-
A.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
B.
usesCharacterArchetype
chosen
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
C.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
D.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
E.
permitsArchetype
Indicates that one entity authorizes or allows the use, presence, or application of a particular archetype in a given context.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 9:01 p.m.