Triple
T37457331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Hand Recruit |
E930831
|
entity |
| Predicate | heroClassThatGenerates |
P100346
|
FINISHED |
| Object | Paladin |
—
|
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: Paladin | Statement: [Silver Hand Recruit, heroClassThatGenerates, Paladin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroClassThatGenerates Context triple: [Silver Hand Recruit, heroClassThatGenerates, Paladin]
-
A.
heroClass
chosen
Indicates the character class or role that a hero belongs to within a given system or context.
-
B.
characterGenerator
Indicates a relationship where an entity produces, defines, or initializes characters or character data for use in another context.
-
C.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
D.
baseHero
Indicates that one entity serves as the primary or foundational hero associated with another entity.
-
E.
hasProtagonistClass
Indicates that a work’s main character belongs to a specified class or category.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.