Triple
T36732328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew–Luke–Mark |
E907373
|
entity |
| Predicate | proposesSecondGospel |
P187015
|
FINISHED |
| Object | Gospel of Luke |
—
|
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: Gospel of Luke | Statement: [Matthew–Luke–Mark, proposesSecondGospel, Gospel of Luke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesSecondGospel Context triple: [Matthew–Luke–Mark, proposesSecondGospel, Gospel of Luke]
-
A.
proposesFirstGospel
Indicates that an entity puts forward or advocates a particular work as the earliest or original gospel in a given context.
-
B.
secondEpistleTitle
Indicates that one entity is the title of a second epistle (second letter) associated with another entity.
-
C.
secondaryScripturalSource
Indicates that one entity serves as a secondary or supporting scriptural reference or authority in relation to another primary scriptural source.
-
D.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
E.
proposesExistenceOf
Indicates that one entity puts forward or suggests that another entity should exist or be brought into existence.
- F. None of above. chosen
Provenance (4 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.