Triple
T27522287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyce Avenue |
E694738
|
entity |
| Predicate | hasYouTubeChannelURL |
P162675
|
FINISHED |
| Object | https://www.youtube.com/user/boyceavenue |
—
|
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: https://www.youtube.com/user/boyceavenue | Statement: [Boyce Avenue, hasYouTubeChannelURL, https://www.youtube.com/user/boyceavenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouTubeChannelURL Context triple: [Boyce Avenue, hasYouTubeChannelURL, https://www.youtube.com/user/boyceavenue]
-
A.
YouTubeChannel
Indicates that an entity is a YouTube channel, i.e., a content-publishing account or channel on the YouTube platform.
-
B.
hasTube
Indicates that one entity possesses, includes, or is equipped with a tube as a component or feature.
-
C.
hasYouTubeMusicVideo
Indicates that an entity has an associated music video available on YouTube.
-
D.
operatesYouTubeChannel
Indicates that one entity manages and runs a YouTube channel as its owner or primary operator.
-
E.
YouTubeChannelName
Indicates the specific name assigned to a YouTube channel that identifies it on the platform.
- F. None of above. chosen
Provenance (4 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f2c6c8c81909de1fbb4f4f5600a |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 1:21 p.m.