Triple
T36732209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustinian hypothesis |
E907370
|
entity |
| Predicate | literarySequence |
P59803
|
FINISHED |
| Object | Matthew precedes Luke |
—
|
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: Matthew precedes Luke | Statement: [Augustinian hypothesis, literarySequence, Matthew precedes Luke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySequence Context triple: [Augustinian hypothesis, literarySequence, Matthew precedes Luke]
-
A.
narrativeSequence
chosen
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
-
B.
literarySeries
Indicates that one work is part of, or belongs to, a larger literary series that connects multiple related works.
-
C.
literarySeriesSubject
Indicates that a work is part of, or concerns, a particular literary series as its subject.
-
D.
literarySeriesGenre
Indicates that a literary series belongs to or is categorized under a particular genre.
-
E.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:12 p.m.