Triple
T22791299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Packaging Conventions |
E564115
|
entity |
| Predicate | supportsInteroperabilityFor |
P48644
|
FINISHED |
| Object | Office documents |
—
|
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: Office documents | Statement: [Open Packaging Conventions, supportsInteroperabilityFor, Office documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteroperabilityFor Context triple: [Open Packaging Conventions, supportsInteroperabilityFor, Office documents]
-
A.
interoperabilityWith
chosen
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
B.
supportsInterconnection
Indicates that one entity enables, facilitates, or maintains a connection or interoperability between two or more other entities.
-
C.
isSupportedFor
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
-
D.
interoperabilityStandard
Indicates that there is a standard or specification enabling different systems, components, or technologies to work together and exchange information seamlessly.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by 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_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.