Triple
T37663058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandon Pearce |
E937757
|
entity |
| Predicate | usesAliasOnPlatform |
P174409
|
FINISHED |
| Object | Kingbdogz on YouTube |
—
|
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: Kingbdogz on YouTube | Statement: [Brandon Pearce, usesAliasOnPlatform, Kingbdogz on YouTube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAliasOnPlatform Context triple: [Brandon Pearce, usesAliasOnPlatform, Kingbdogz on YouTube]
-
A.
usesAliasIn
chosen
Indicates that one entity operates under or refers to another entity by an alternative name or alias within a specific context.
-
B.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
C.
usesAliasWith
Indicates that one entity employs or operates under an alternative name or identifier in association with another entity.
-
D.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
-
E.
usesAliasConvention
Indicates that one entity adopts or follows a specific alias-naming convention when referring to another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.