Triple
T27034333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Save The Crew |
E681010
|
entity |
| Predicate | usedHashtag |
P123024
|
FINISHED |
| Object | #SaveTheCrew |
—
|
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: #SaveTheCrew | Statement: [Save The Crew, usedHashtag, #SaveTheCrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHashtag Context triple: [Save The Crew, usedHashtag, #SaveTheCrew]
-
A.
usedInHashtag
chosen
Indicates that something (such as a word, phrase, or entity) is employed as part of a hashtag.
-
B.
hashtag
Indicates that an entity is associated with or labeled by a specific hashtag, typically used for categorization or topic tagging.
-
C.
hasOfficialHashtag
Indicates that an entity is associated with a designated official hashtag used for identification or promotion.
-
D.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
E.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62266b8b48190a050b4953753e5a7 |
completed | May 2, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:15 a.m.