Triple
T13094554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Is That All There Is? |
E310548
|
entity |
| Predicate | hasSpokenWordSections |
P108014
|
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: [Is That All There Is?, hasSpokenWordSections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenWordSections Context triple: [Is That All There Is?, hasSpokenWordSections, true]
-
A.
hasSpokenWordIntro
Indicates that an entity includes or features an introductory segment performed in spoken word form.
-
B.
hasSpokenWordVerses
Indicates that an entity (such as a work or recording) contains or features verses performed in spoken word form.
-
C.
includesSpokenWordAppearanceBy
Indicates that something (such as a work, recording, or event) contains an instance where a person or entity appears through spoken words.
-
D.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
E.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.