Triple
T1433180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke the Evangelist |
E30495
|
entity |
| Predicate | gospelPosition |
P13852
|
FINISHED |
| Object | third gospel in the New Testament |
—
|
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: third gospel in the New Testament | Statement: [Luke the Evangelist, gospelPosition, third gospel in the New Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gospelPosition Context triple: [Luke the Evangelist, gospelPosition, third gospel in the New Testament]
-
A.
positionAmongGospels
chosen
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
B.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
C.
discPosition
Indicates the spatial or ordinal placement of a disc relative to a reference point or within a set or structure.
-
D.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
E.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.