Triple
T24306237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabaa hand gesture |
E612542
|
entity |
| Predicate | hasDigitalHashtag |
P9354
|
FINISHED |
| Object | #R4bia |
—
|
NE NERFINISHED |
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: #R4bia | Statement: [Rabaa hand gesture, hasDigitalHashtag, #R4bia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalHashtag Context triple: [Rabaa hand gesture, hasDigitalHashtag, #R4bia]
-
A.
hasOfficialHashtag
Indicates that an entity is associated with a designated official hashtag used for identification or promotion.
-
B.
hashtag
chosen
Indicates that an entity is associated with or labeled by a specific hashtag, typically used for categorization or topic tagging.
-
C.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
D.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
E.
usedInHashtag
Indicates that something (such as a word, phrase, or entity) is employed as part of a hashtag.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292272af88190b9c23615adbac911 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:30 a.m.