Triple
T34794175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabriel Conroy |
E1003023
|
entity |
| Predicate | basedInWorkPublishedIn |
P103115
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Gabriel Conroy, basedInWorkPublishedIn, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInWorkPublishedIn Context triple: [Gabriel Conroy, basedInWorkPublishedIn, 1914]
-
A.
basedOnWorkAppearedIn
Indicates that something is derived from, adapted from, or otherwise created using a work that appeared in a specified source or publication.
-
B.
basedOnWorkAppearsIn
Indicates that one work is derived from or informed by another work in which it appears or is featured.
-
C.
workInThisPublication
Indicates that an entity performs work or contributes within the context of the specified publication.
-
D.
createdInWorkPublishedIn
chosen
Indicates that something was created within a work that was subsequently published in a particular publication or venue.
-
E.
basedOnWorkPublisher
Indicates that one entity serves as the publisher of the work on which another entity is based.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 3, 2026, 3:59 p.m.