Triple
T38643959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Void Elves |
E938669
|
entity |
| Predicate | racialCustomization |
P118447
|
FINISHED |
| Object | Void-themed hairstyles |
—
|
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: Void-themed hairstyles | Statement: [Void Elves, racialCustomization, Void-themed hairstyles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialCustomization Context triple: [Void Elves, racialCustomization, Void-themed hairstyles]
-
A.
rimCharacteristic
Indicates a specific property or feature that characterizes a rim in the context of its structure, design, or function.
-
B.
racialIdentity
Indicates the relationship between an entity and the racial group or classification with which it is identified or categorized.
-
C.
notableRaceCharacteristic
chosen
Indicates that an entity is distinguished by a particular race-related trait or attribute that is especially prominent or noteworthy.
-
D.
raceRole
Indicates the specific role, position, or function an entity holds within a race or racing event.
-
E.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:32 p.m.