Triple
T20182739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roshambo |
E492772
|
entity |
| Predicate | usesHandGestures |
P139008
|
FINISHED |
| Object | rock |
—
|
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: rock | Statement: [Roshambo, usesHandGestures, rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHandGestures Context triple: [Roshambo, usesHandGestures, rock]
-
A.
recognizedSignLanguage
Indicates that one entity has correctly identified or understood a sign language used or produced by another entity.
-
B.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
C.
usesSignLanguage
Indicates that one entity communicates using sign language with or in relation to another entity.
-
D.
openingGesture
Indicates an initial movement or action that begins or invites the start of an interaction, event, or sequence.
-
E.
hasMotionControls
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ef9370819091a8479f811002a9 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:36 p.m.