Triple
T34578151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Couve |
E887815
|
entity |
| Predicate | usedInSocialMedia |
P186294
|
FINISHED |
| Object | hashtags related to Vancouver, Washington |
—
|
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: hashtags related to Vancouver, Washington | Statement: [The Couve, usedInSocialMedia, hashtags related to Vancouver, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSocialMedia Context triple: [The Couve, usedInSocialMedia, hashtags related to Vancouver, Washington]
-
A.
usedOnSocialMedia
chosen
Indicates that something is employed, shared, or referenced within social media platforms or interactions.
-
B.
mediaUse
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
C.
usedInHashtag
Indicates that something (such as a word, phrase, or entity) is employed as part of a hashtag.
-
D.
usedByMediaIn
Indicates that something is employed or utilized within a particular media work or medium.
-
E.
usedInDigitalMedia
Indicates that something is employed, featured, or incorporated within digital media content or platforms.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 2:03 a.m.