Triple
T38644180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulpera |
E938673
|
entity |
| Predicate | racialClassAvailability |
P192416
|
FINISHED |
| Object | Warrior |
—
|
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: Warrior | Statement: [Vulpera, racialClassAvailability, Warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialClassAvailability Context triple: [Vulpera, racialClassAvailability, Warrior]
-
A.
racialClass
Indicates a classification relationship where an entity is assigned to or associated with a particular racial category or group.
-
B.
racialClassAffinity
Indicates a relationship where an entity has a particular affinity, connection, or alignment with a specified racial class.
-
C.
raceQualification
Indicates that an entity meets the necessary criteria or standards to participate in a particular race or competitive event.
-
D.
racialStructure
Indicates how racial categories or groupings are organized, distributed, or structured within a given context or system.
-
E.
raceGroup
Indicates that the subject belongs to, or is categorized within, a particular racial or ethnic group.
- F. None of above. chosen
Provenance (4 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: May 3, 2026, 4:32 p.m.