Triple
T27727943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | stoning of Paul |
E697352
|
entity |
| Predicate | describedInVerses |
P519
|
FINISHED |
| Object | Acts 14:19–20 |
—
|
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: Acts 14:19–20 | Statement: [stoning of Paul, describedInVerses, Acts 14:19–20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedInVerses Context triple: [stoning of Paul, describedInVerses, Acts 14:19–20]
-
A.
commonlyPerformedVerses
Indicates that certain verses are frequently performed or recited in practice, relative to others.
-
B.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
C.
positionInScripture
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
D.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
E.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 3:10 p.m.