Triple
T21556603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas the Israelite |
E531907
|
entity |
| Predicate | religiousGenreOfWork |
P21942
|
FINISHED |
| Object | infancy gospel |
—
|
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: infancy gospel | Statement: [Thomas the Israelite, religiousGenreOfWork, infancy gospel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousGenreOfWork Context triple: [Thomas the Israelite, religiousGenreOfWork, infancy gospel]
-
A.
religiousGenre
chosen
Indicates that the subject is associated with or categorized under a religious genre, style, or tradition.
-
B.
genreOfWorkPerformedIn
Indicates that a specified genre characterizes the type of work that is performed in a particular event, context, or setting.
-
C.
genreOfProducedWorks
Indicates that one entity is the genre category to which the works produced by another entity belong.
-
D.
genreOfWorkDescribedIn
Indicates that a work is characterized as belonging to a particular genre as described in another resource or context.
-
E.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e04b048190ac3a9913094b4625 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.