Triple
T22791297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Packaging Conventions |
E564115
|
entity |
| Predicate | definesContentTypePart |
P125591
|
FINISHED |
| Object | [Content_Types].xml |
—
|
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: [Content_Types].xml | Statement: [Open Packaging Conventions, definesContentTypePart, [Content_Types].xml]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesContentTypePart Context triple: [Open Packaging Conventions, definesContentTypePart, [Content_Types].xml]
-
A.
addsContentType
Indicates that one entity augments or associates another entity with a specific content type.
-
B.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
C.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
D.
governsContentType
chosen
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
E.
producedContentType
Indicates that an entity has created or generated content of a specified type or format.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c3545fc819084af67cc25e94839 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.