Triple
T28014250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrow’s World |
E707502
|
entity |
| Predicate | featuredTopic |
P26448
|
FINISHED |
| Object | home computing |
—
|
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: home computing | Statement: [Tomorrow’s World, featuredTopic, home computing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredTopic Context triple: [Tomorrow’s World, featuredTopic, home computing]
-
A.
featuresTopic
chosen
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
-
B.
featuredIssue
Indicates that an issue is highlighted or given special prominence relative to other issues.
-
C.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
D.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
E.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
- F. None of above.
Provenance (3 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 27, 2026, 8:05 p.m.