Triple
T20392708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcans |
E498121
|
entity |
| Predicate | saluteGesture |
P16866
|
FINISHED |
| Object | raised hand with parted middle and ring fingers |
—
|
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: raised hand with parted middle and ring fingers | Statement: [Vulcans, saluteGesture, raised hand with parted middle and ring fingers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saluteGesture Context triple: [Vulcans, saluteGesture, raised hand with parted middle and ring fingers]
-
A.
gesture
chosen
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
B.
saluteStatus
Indicates the type or state of a salute being given or received between entities (e.g., whether, how, or in what manner one entity salutes another).
-
C.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
D.
openingGesture
Indicates an initial movement or action that begins or invites the start of an interaction, event, or sequence.
-
E.
armsGiveRiseTo
Indicates that the presence or characteristics of arms lead to, cause, or generate another condition, feature, or outcome.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6791144788190a0ab42cf0141b6a3 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.