Triple
T16850478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The One (2001 film) |
E409659
|
entity |
| Predicate | hasFightChoreographyStyle |
P12046
|
FINISHED |
| Object | martial arts |
—
|
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: martial arts | Statement: [The One (2001 film), hasFightChoreographyStyle, martial arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFightChoreographyStyle Context triple: [The One (2001 film), hasFightChoreographyStyle, martial arts]
-
A.
choreographyStyle
chosen
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
-
C.
hasChoreographicLegacy
Indicates that one entity has a lasting influence or recognized heritage in choreography that is derived from or shaped by another entity.
-
D.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
E.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b378dda48190ab81d75f2cfe3ab3 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.