Triple
T28658819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Musketeer |
E725407
|
entity |
| Predicate | fightChoreographyStyle |
P12046
|
FINISHED |
| Object | Hong Kong action cinema |
—
|
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: Hong Kong action cinema | Statement: [The Musketeer, fightChoreographyStyle, Hong Kong action cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightChoreographyStyle Context triple: [The Musketeer, fightChoreographyStyle, Hong Kong action cinema]
-
A.
choreographyStyle
chosen
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
-
B.
hasFightSequencesChoreographyBy
Indicates that the fight sequences in a work are choreographed by a specified person or entity.
-
C.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
D.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
E.
打撃スタイル
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:56 a.m.