Triple
T7933680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDocument format |
E184239
|
entity |
| Predicate | primaryTextFormat |
P130
|
FINISHED |
| Object | .odt |
—
|
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: .odt | Statement: [OpenDocument format, primaryTextFormat, .odt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTextFormat Context triple: [OpenDocument format, primaryTextFormat, .odt]
-
A.
primaryTextUsed
Indicates that a particular text is the main or principal textual content used in relation to another entity or resource.
-
B.
primaryStyle
Indicates the main or predominant style associated with an entity, distinguishing it from other secondary or supporting styles.
-
C.
textMode
Indicates that something operates, is displayed, or is processed in a mode where information is handled primarily as text rather than as graphics or other media.
-
D.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
firstPartFormat
Indicates that the subject entity is the initial segment or portion in the overall format or structured sequence of something.
- 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.