Triple
T32988376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gray Sports Publishing |
E844008
|
entity |
| Predicate | associatedFictionalWorkFormat |
P116835
|
FINISHED |
| Object | book |
—
|
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: book | Statement: [Gray Sports Publishing, associatedFictionalWorkFormat, book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFictionalWorkFormat Context triple: [Gray Sports Publishing, associatedFictionalWorkFormat, book]
-
A.
hasFormatInFiction
chosen
Indicates that a work of fiction is presented or realized in a particular narrative or media format (e.g., novel, film, comic).
-
B.
hasAssociatedWorkOfFiction
Indicates that an entity is linked to a related work of fiction, such as a novel, film, or story that is associated with it.
-
C.
relatedFormat
Indicates that two resources are available in different but closely related formats or media representations of essentially the same content.
-
D.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
E.
isForFictionalWork
Indicates that something is intended to be used in, associated with, or specifically created for a fictional work.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:22 a.m.