Triple
T902109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sports Illustrated for Kids |
E19468
|
entity |
| Predicate | readingExperience |
P20180
|
FINISHED |
| Object | engaging |
—
|
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: engaging | Statement: [Sports Illustrated for Kids, readingExperience, engaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingExperience Context triple: [Sports Illustrated for Kids, readingExperience, engaging]
-
A.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
-
B.
requiredReadingFor
Indicates that one item (such as a text or resource) must be read as a mandatory prerequisite or component for engaging with, understanding, or completing another item (such as a course, assignment, or program).
-
C.
book
Indicates that an agent reserves or schedules a service, event, or resource for future use.
-
D.
readBy
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
-
E.
book5Content
Indicates that one entity is the content or textual material contained within the book represented by the other entity.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4412408190a6bf8fc7484a5781 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa98caec8190bbcc38320090f058 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab60fea8819098ce3269181897d1 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.