Triple
T8421524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raycon |
E198865
|
entity |
| Predicate | hasEndorsementStyle |
P1609
|
FINISHED |
| Object | celebrity endorsements |
—
|
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: celebrity endorsements | Statement: [Raycon, hasEndorsementStyle, celebrity endorsements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndorsementStyle Context triple: [Raycon, hasEndorsementStyle, celebrity endorsements]
-
A.
hasContractStyle
Indicates that one entity is associated with or characterized by a particular contract style or contractual format.
-
B.
hasEndorser
Indicates that one entity supports, approves, or publicly backs another entity, typically lending it credibility or validation.
-
C.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from others.
-
D.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
E.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84ca7b348190abab25e79b05407f |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.