Triple
T29120278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QT-1 |
E737159
|
entity |
| Predicate | publicationIncludedIn |
P309
|
FINISHED |
| Object | I, Robot (1950 collection) |
—
|
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: I, Robot (1950 collection) | Statement: [QT-1, publicationIncludedIn, I, Robot (1950 collection)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationIncludedIn Context triple: [QT-1, publicationIncludedIn, I, Robot (1950 collection)]
-
A.
publishedIn
chosen
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
B.
publishedInPart
Indicates that a work or content item was released or made available only as a portion or installment within a larger publication or series.
-
C.
appearsInPublication
Indicates that an entity is featured, mentioned, or discussed within a specific publication.
-
D.
publishedDocument
Indicates that an entity has formally issued or made a document publicly available.
-
E.
publicationOpus
Indicates that a work or opus has been published, linking the creative work to its publication event or status.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 28, 2026, 11:25 a.m.