Triple
T7933683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDocument format |
E184239
|
entity |
| Predicate | primaryGraphicsFormat |
P13218
|
FINISHED |
| Object | .odg |
—
|
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: .odg | Statement: [OpenDocument format, primaryGraphicsFormat, .odg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGraphicsFormat Context triple: [OpenDocument format, primaryGraphicsFormat, .odg]
-
A.
typicalPictureFormat
chosen
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
-
B.
primaryTexture
Indicates that one entity serves as the main or dominant surface texture characterizing another entity.
-
C.
formerPictureFormat
Indicates that an entity previously used a particular picture format before changing to a different one.
-
D.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
E.
supportsHDRFormat
Indicates that one entity is capable of handling, displaying, or processing content encoded in a specified High Dynamic Range (HDR) format for 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.