Triple
T24204172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Can't See Me |
E600055
|
entity |
| Predicate | basedOnPersona |
P155184
|
FINISHED |
| Object | John Cena rap persona |
—
|
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: John Cena rap persona | Statement: [You Can't See Me, basedOnPersona, John Cena rap persona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPersona Context triple: [You Can't See Me, basedOnPersona, John Cena rap persona]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
basedOnSubject
Indicates that something is derived from, influenced by, or determined according to a particular subject.
-
C.
basedOnType
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
D.
basedOnSetting
Indicates that one entity is derived from, influenced by, or constructed using the setting or contextual environment defined by another entity.
-
E.
basedOnQuestion
Indicates that something is derived from, informed by, or constructed in response to a specific question.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:37 p.m.