Triple
T21875076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crips |
E540115
|
entity |
| Predicate | associatedWithHandSign |
P63976
|
FINISHED |
| Object | C-shaped hand sign |
—
|
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: C-shaped hand sign | Statement: [Crips, associatedWithHandSign, C-shaped hand sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHandSign Context triple: [Crips, associatedWithHandSign, C-shaped hand sign]
-
A.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
B.
recognizedSignLanguage
Indicates that one entity has correctly identified or understood a sign language used or produced by another entity.
-
C.
handMeaning
Indicates that one entity uses or positions its hand in a particular way to convey a specific meaning, message, or communicative intent toward another entity.
-
D.
signAssociated
chosen
Indicates that one entity is associated with, represented by, or linked to a particular sign or symbol of another entity.
-
E.
servedAsHandTo
Indicates that one entity functioned as an assistant, aide, or subordinate support to another entity in carrying out tasks or responsibilities.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33957f481908789b054a4fd1b77 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:02 p.m.