Triple
T13796224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cecep Arif Rahman |
E331520
|
entity |
| Predicate | notableAppearanceType |
P111491
|
FINISHED |
| Object | hand-to-hand combat scenes |
—
|
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: hand-to-hand combat scenes | Statement: [Cecep Arif Rahman, notableAppearanceType, hand-to-hand combat scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAppearanceType Context triple: [Cecep Arif Rahman, notableAppearanceType, hand-to-hand combat scenes]
-
A.
notableAppearance
Indicates that an entity is prominently featured or makes a significant appearance in another work, event, or context.
-
B.
notableAppearanceIn
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
-
C.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
D.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
E.
hasNotableMultipleAppearances
Indicates that an entity appears multiple times in a context or medium in a way considered significant or noteworthy.
- F. None of above. chosen
Provenance (4 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025be1f08190aac525d72d7dc0c3 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.