Triple
T36732183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustinian hypothesis |
E907370
|
entity |
| Predicate | placesSecond |
P62306
|
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: [Augustinian hypothesis, placesSecond, Gospel of Luke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesSecond Context triple: [Augustinian hypothesis, placesSecond, Gospel of Luke]
-
A.
secondPlace
Indicates that an entity holds the position of runner-up or finishes in second place in a ranked ordering, competition, or comparison relative to others.
-
B.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
-
C.
secondElement
chosen
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
-
D.
secondEditionThirdPlace
Indicates that something is the third-place finisher or ranking in the second edition of a given event, competition, or listing.
-
E.
secondLargestTownIn
Indicates that one town is the second largest town (by size or population) within a specified region or administrative area.
- 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:12 p.m.