Triple
T4170883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Story Weekly |
E84558
|
entity |
| Predicate | workPublished |
P35758
|
FINISHED |
| Object | stories featuring Zorro |
—
|
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: stories featuring Zorro | Statement: [All-Story Weekly, workPublished, stories featuring Zorro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPublished Context triple: [All-Story Weekly, workPublished, stories featuring Zorro]
-
A.
publicationAbout
chosen
Indicates that a publication has content whose subject or focus is the referenced entity.
-
B.
publicationCompleted
Indicates that the process of publishing an item (such as a document, work, or release) has been fully finished and made officially available.
-
C.
publishesWorkFrom
Indicates that an entity (such as a publisher or platform) issues or makes public a work that originates from a particular source entity.
-
D.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
E.
formerPublication
Indicates that an entity was previously published in, or associated as a publication with, another entity but is no longer currently so.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c87cc88190a9ec3712db18a8a7 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.