Triple
T18282504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seraphim |
E437896
|
entity |
| Predicate | locationInIsaiah6 |
P131167
|
FINISHED |
| Object | around the throne of God |
—
|
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: around the throne of God | Statement: [Seraphim, locationInIsaiah6, around the throne of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInIsaiah6 Context triple: [Seraphim, locationInIsaiah6, around the throne of God]
-
A.
positionInScripture
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
B.
locatedInTheChurch
Indicates that one entity is physically situated within or inside the church.
-
C.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
D.
locationOfPassage
Indicates the place or area through which a passage, route, or transit occurs or is situated.
-
E.
positionOnJerusalem
Indicates that one entity occupies or is located at a specific position within the area of Jerusalem.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50057c5c881909fcda72f4a98c8c3 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.