Triple
T30447169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omniversum |
E774609
|
entity |
| Predicate | screenDiameter |
P172843
|
FINISHED |
| Object | approximately 18 meters |
—
|
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: approximately 18 meters | Statement: [Omniversum, screenDiameter, approximately 18 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenDiameter Context triple: [Omniversum, screenDiameter, approximately 18 meters]
-
A.
screenCapacity
Indicates the maximum number of items or content units that can be displayed on a screen at one time.
-
B.
rearScreenSize
Indicates the size or dimensions of a device’s rear display screen.
-
C.
screenCurvature
Indicates that one entity has a specific degree or type of curvature in its screen surface relative to another entity or a defined standard.
-
D.
screenToBodyRatio
Indicates the proportion of a device’s front surface area that is occupied by its screen.
-
E.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 29, 2026, 8:09 p.m.