Triple
T37554271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azuresong Mageblade |
E933656
|
entity |
| Predicate | isCasterOriented |
P188281
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Azuresong Mageblade, isCasterOriented, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCasterOriented Context triple: [Azuresong Mageblade, isCasterOriented, true]
-
A.
usesCastingOf
Indicates that one entity employs or applies a particular casting of another entity (such as a type, role, or form) in its operation or context.
-
B.
isCastingCategoryFor
Indicates that one entity serves as the casting category or type classification used to group or select another entity in a casting context.
-
C.
hasCasting
Indicates that an entity features a particular actor or set of actors in its cast.
-
D.
hasCastRotationBy
Indicates that one entity’s cast or lineup is rotated, scheduled, or cycled according to another entity (such as a rule, pattern, or rotation scheme).
-
E.
hasRelativeInCast
Indicates that an individual has a family member who is part of the cast of a given production.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.