Triple
T30875958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omni |
E786475
|
entity |
| Predicate | scripturalAbbreviation |
P123091
|
FINISHED |
| Object | Omni |
—
|
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: Omni | Statement: [Omni, scripturalAbbreviation, Omni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalAbbreviation Context triple: [Omni, scripturalAbbreviation, Omni]
-
A.
abbreviationScript
chosen
Indicates that one entity is an abbreviated form of another entity written in a specific script or writing system.
-
B.
scripturalAllusion
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
C.
scriptureAllusion
Indicates that one entity makes reference to, echoes, or is inspired by a passage, theme, or element from a scriptural text found in another entity.
-
D.
scripturalCorpus
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
-
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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 8:48 p.m.