Triple
T36592676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippians 4:4–5 |
E902711
|
entity |
| Predicate | verseStart |
P185910
|
FINISHED |
| Object | Philippians 4:4 |
—
|
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: Philippians 4:4 | Statement: [Philippians 4:4–5, verseStart, Philippians 4:4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verseStart Context triple: [Philippians 4:4–5, verseStart, Philippians 4:4]
-
A.
verseBefore
Indicates that one verse occurs earlier in the ordered sequence of verses than another verse.
-
B.
verseAfter
Indicates that one verse occurs immediately later in sequence than another verse within the same ordered text.
-
C.
verse3
Indicates a relationship where one entity is the third verse or stanza associated with another entity, such as a song, poem, or scripture passage.
-
D.
verseNumber
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
-
E.
verse
Indicates that one entity is in opposition or conflict against another, as in a competitive or adversarial relationship.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.