Triple
T6529712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betcha Gon’ Know (The Prologue) |
E152197
|
entity |
| Predicate | hasPrologueInTitle |
P71438
|
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: [Betcha Gon’ Know (The Prologue), hasPrologueInTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrologueInTitle Context triple: [Betcha Gon’ Know (The Prologue), hasPrologueInTitle, true]
-
A.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
-
B.
includesSpokenPrologue
Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
hasProperPreface
Indicates that an entity is accompanied by an appropriate and correctly structured introductory preface.
-
E.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adaafbfc8190a3e3c75ea5958c67 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:46 p.m.