Triple
T37470510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadjia the Mistblade |
E931139
|
entity |
| Predicate | combatTheme |
P183281
|
FINISHED |
| Object | dueling and single-target focus |
—
|
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: dueling and single-target focus | Statement: [Nadjia the Mistblade, combatTheme, dueling and single-target focus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatTheme Context triple: [Nadjia the Mistblade, combatTheme, dueling and single-target focus]
-
A.
battleTheme
chosen
Indicates that a particular piece of music or motif is used or associated as the theme during a battle or combat encounter between entities.
-
B.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
C.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
D.
combatApplication
Indicates the application or use of something (such as skills, tactics, or equipment) within a combat or fighting context.
-
E.
combatView
Indicates a perspective or representation of entities engaged in combat or battle-related interaction.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.