Triple
T33479520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Nevill |
E857428
|
entity |
| Predicate | hasSelfPublishedThrough |
P72106
|
FINISHED |
| Object | Ritual Limited |
—
|
NE NERFINISHED |
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: Ritual Limited | Statement: [Adam Nevill, hasSelfPublishedThrough, Ritual Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelfPublishedThrough Context triple: [Adam Nevill, hasSelfPublishedThrough, Ritual Limited]
-
A.
selfPublished
chosen
Indicates that an entity has published its own work independently, without an external publisher.
-
B.
hasAuthorPublished
Indicates that a specific author has produced and made publicly available at least one work, such as a book, article, or paper.
-
C.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
D.
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.
-
E.
hasPub
Indicates that an entity is associated with, or has access to, a public house (pub) as a related establishment or feature.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 1, 2026, 1:38 a.m.