Triple
T9129027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRSVue Pew Bible editions |
E219035
|
entity |
| Predicate | textLayoutGoal |
P87262
|
FINISHED |
| Object | clarity |
—
|
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: clarity | Statement: [NRSVue Pew Bible editions, textLayoutGoal, clarity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textLayoutGoal Context triple: [NRSVue Pew Bible editions, textLayoutGoal, clarity]
-
A.
textAlignment
Indicates how text is positioned or aligned relative to a reference frame, such as margins, columns, or other layout boundaries.
-
B.
coreText
Indicates that something serves as the main or primary textual content within a larger work or context.
-
C.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
D.
textCharacter
Indicates that one entity is a character (such as a letter, digit, or symbol) within a piece of text associated with another entity.
-
E.
orthographicGoal
Indicates that one entity has the intended or target written/orthographic form of another entity.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cc85b081908ee80db0e3b7df15 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:18 p.m.