Triple
T37464043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilliax |
E930989
|
entity |
| Predicate | canBePlayedByClass |
P189391
|
FINISHED |
| Object | Druid |
—
|
NE NERFINISHED |
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: Druid | Statement: [Zilliax, canBePlayedByClass, Druid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePlayedByClass Context triple: [Zilliax, canBePlayedByClass, Druid]
-
A.
playableInClass
chosen
Indicates that something (such as a skill, item, or ability) can be used or is valid for use within a particular class or category.
-
B.
cannotPlayClass
Indicates that a given entity is not allowed or able to participate in or use a specified class.
-
C.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
D.
playableClasses
Indicates that the referenced entity can be used or selected as a character class that a player is allowed to play.
-
E.
canAlsoBePlayedIn
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
- 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_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.