Triple
T28349568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Would You Rather? |
E718053
|
entity |
| Predicate | hasStandaloneScenes |
P193465
|
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: [Would You Rather?, hasStandaloneScenes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandaloneScenes Context triple: [Would You Rather?, hasStandaloneScenes, true]
-
A.
numberOfScenes
Indicates the total count of distinct scenes associated with or contained within an entity.
-
B.
hasStandaloneGame
Indicates that an entity has its own independently released, self-contained game associated with it.
-
C.
hasStagedSceneAs
Indicates that one entity has arranged, directed, or presented another entity in a particular scene or setting, typically for performance, display, or representation.
-
D.
hasStandaloneTales
Indicates that an entity includes or is associated with independent, self-contained stories that can be understood without relying on a larger narrative.
-
E.
hasRegionalScene
Indicates that something possesses or is associated with a specific regional scene, such as a localized cultural, artistic, or social milieu.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: April 28, 2026, 12:45 a.m.