Triple
T7073104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathakali |
E164747
|
entity |
| Predicate | usesGestureSystem |
P40440
|
FINISHED |
| Object | mudras |
—
|
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: mudras | Statement: [Kathakali, usesGestureSystem, mudras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGestureSystem Context triple: [Kathakali, usesGestureSystem, mudras]
-
A.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
B.
hasStylus
Indicates that an entity possesses or is equipped with a stylus as an accessory or tool.
-
C.
hasMotionControls
chosen
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
D.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
E.
usesFingerspellingSystem
Indicates that one entity employs or applies a particular fingerspelling system in communication or representation.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4cb76548190bd98876f8ba925b7 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.