Triple
T38583365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulpera |
E932292
|
entity |
| Predicate | racialPassive |
P181486
|
FINISHED |
| Object | Fire resistance bonus |
—
|
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: Fire resistance bonus | Statement: [Vulpera, racialPassive, Fire resistance bonus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialPassive Context triple: [Vulpera, racialPassive, Fire resistance bonus]
-
A.
raceRole
Indicates the specific role, position, or function an entity holds within a race or racing event.
-
B.
racialClass
Indicates a classification relationship where an entity is assigned to or associated with a particular racial category or group.
-
C.
racialAbility
chosen
Indicates a relationship where a particular race or ethnicity is associated with a specific ability, trait, or power.
-
D.
racialIdentity
Indicates the relationship between an entity and the racial group or classification with which it is identified or categorized.
-
E.
raceRepresentation
Indicates how different races or ethnic groups are portrayed, included, or reflected within a given context, medium, or setting.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:32 p.m.