Triple
T5531959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amadeus |
E145068
|
entity |
| Predicate | runtimeDirectorCut |
P37393
|
FINISHED |
| Object | 180 minutes |
—
|
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: 180 minutes | Statement: [Amadeus, runtimeDirectorCut, 180 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimeDirectorCut Context triple: [Amadeus, runtimeDirectorCut, 180 minutes]
-
A.
hasDirectorCut
chosen
Indicates that a work (such as a film or episode) has an alternative version edited according to the director’s preferred vision.
-
B.
movementDirector
Indicates that one entity serves as the movement director (responsible for choreographing or directing movement) for another entity, such as a performance or production.
-
C.
cutRule
Indicates that one entity applies or enforces a rule that removes, prunes, or eliminates certain elements or possibilities from consideration.
-
D.
scriptDirection
Indicates the direction in which a writing system or script is read or written (e.g., left-to-right, right-to-left, top-to-bottom).
-
E.
remakeDirector
Indicates that the subject is the director of a remake of the object work (e.g., film, show, or other media).
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f9d17ec8190b93b12931a4c1b33 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.