Triple
T1601655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team LeBron players wore number 2 jerseys in honor of Gianna Bryant |
E34405
|
entity |
| Predicate | typeOfGesture |
P16866
|
FINISHED |
| Object | memorial tribute |
—
|
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: memorial tribute | Statement: [Team LeBron players wore number 2 jerseys in honor of Gianna Bryant, typeOfGesture, memorial tribute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGesture Context triple: [Team LeBron players wore number 2 jerseys in honor of Gianna Bryant, typeOfGesture, memorial tribute]
-
A.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
B.
gripType
Indicates the manner or style in which one entity physically holds or grasps another.
-
C.
gesture
chosen
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
D.
hasGripType
Indicates that one entity possesses or uses a specific type or style of grip in relation to another entity or action.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.