Triple
T24857608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Editorial Tor |
E622068
|
entity |
| Predicate | hasPublishedFormat |
P5128
|
FINISHED |
| Object | print books |
—
|
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: print books | Statement: [Editorial Tor, hasPublishedFormat, print books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublishedFormat Context triple: [Editorial Tor, hasPublishedFormat, print books]
-
A.
hasPublishingFormat
chosen
Indicates that an entity is associated with a specific format or medium in which it is published or made publicly available.
-
B.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
C.
hasPublishedOn
Indicates that an entity (such as an author or publisher) has released or made content publicly available on a particular platform, medium, or date.
-
D.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
E.
isPublishedWith
Indicates that an entity is released or made publicly available together with another specified entity, typically as part of the same publication or release event.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:21 a.m.