Triple
T31371336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There’s More to Life Than This |
E800169
|
entity |
| Predicate | featuresLiveElements |
P202360
|
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: [There’s More to Life Than This, featuresLiveElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLiveElements Context triple: [There’s More to Life Than This, featuresLiveElements, true]
-
A.
featuresElementSystem
Indicates that a system includes or incorporates a particular element as one of its constituent parts or components.
-
B.
featuresRecurringElement
Indicates that something includes an element, motif, or component that appears repeatedly over time or across multiple instances.
-
C.
featuredElement
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
featuresTrapElements
Indicates that something includes or incorporates trap-related elements as part of its structure or design.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
| PDg | Predicate description generation | batch_6a0076bfd1a481909170c3e181a16d9a |
completed | May 10, 2026, 12:14 p.m. |
Created at: April 29, 2026, 9:18 p.m.