Triple
T8800241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lessons in Life and Business |
E209386
|
entity |
| Predicate | describesContentType |
P84700
|
FINISHED |
| Object | personal philosophies |
—
|
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: personal philosophies | Statement: [Lessons in Life and Business, describesContentType, personal philosophies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesContentType Context triple: [Lessons in Life and Business, describesContentType, personal philosophies]
-
A.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
B.
offersContentType
Indicates that one entity provides or makes available content of a specified type to another entity or context.
-
C.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
D.
notableContentType
Indicates the type or category of content for which an entity is notable or best known.
-
E.
broadcastsContentType
Indicates that an entity (such as a broadcaster or channel) transmits or distributes content of a specified type.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb8aab88190befed16301e08efc |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:44 p.m.