Triple
T28191287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beautiful (song) |
E716320
|
entity |
| Predicate | FutureFullName |
P164659
|
FINISHED |
| Object | Nayvadius DeMun Cash |
—
|
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: Nayvadius DeMun Cash | Statement: [Beautiful (song), FutureFullName, Nayvadius DeMun Cash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FutureFullName Context triple: [Beautiful (song), FutureFullName, Nayvadius DeMun Cash]
-
A.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
C.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
D.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
-
E.
fullGivenNameOf
Indicates that one entity is the complete, formal given name corresponding to another entity (such as a person or identifier).
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 27, 2026, 10:25 p.m.