Triple
T7348913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Qurans |
E169443
|
entity |
| Predicate | layoutFeature |
P32581
|
FINISHED |
| Object | few lines of text per page |
—
|
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: few lines of text per page | Statement: [Blue Qurans, layoutFeature, few lines of text per page]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutFeature Context triple: [Blue Qurans, layoutFeature, few lines of text per page]
-
A.
layoutOptions
Indicates how elements are arranged or positioned relative to each other within a given space or structure.
-
B.
layoutDetail
chosen
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
C.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
D.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
E.
displaysFeature
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of 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_69c68a5878888190968ce4d04db8d69f |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.