Triple
T8733623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronin |
E207317
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Ronin |
E207317
|
NE 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: Ronin | Statement: [Ronin, title, Ronin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ronin Context triple: [Ronin, title, Ronin]
-
A.
Ronin
chosen
Ronin is a 1998 action thriller film directed by John Frankenheimer, best known for its intricate espionage plot and realistic, high-intensity car chases set in France.
-
B.
Samurai
Samurai is a spinning thrill ride at Thorpe Park in the UK known for its intense, disorienting inversions and high-speed rotations.
-
C.
47 Ronin
47 Ronin is a 2013 fantasy action film loosely inspired by the Japanese legend of the forty-seven rōnin, blending samurai drama with supernatural elements.
-
D.
Shinya
Shinya is a Japanese given name commonly used for males.
-
E.
Blade of the 47 Ronin
Blade of the 47 Ronin is a modern action-fantasy film that continues the samurai-themed story of the original 47 Ronin with a contemporary, supernatural twist.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d2a26988190acfda17f232e610a |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf292d71ec819082095cb7b8b2d39c |
completed | April 3, 2026, 2:42 a.m. |
Created at: March 30, 2026, 6:37 p.m.