Triple
T13600050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playtime Is Over |
E324918
|
entity |
| Predicate | featuresBoldPersona |
P110253
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Playtime Is Over, featuresBoldPersona, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBoldPersona Context triple: [Playtime Is Over, featuresBoldPersona, true]
-
A.
stagePersonaOf
Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
-
B.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
C.
characterDescription
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
D.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
E.
characterSetting
Indicates that a character is associated with, appears in, or is situated within a particular setting or environment.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0795acc8190a08667ab9dcb0d44 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.