Triple
T30370099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interoperable Master Format |
E772523
|
entity |
| Predicate | usesContainer |
P185956
|
FINISHED |
| Object | MXF |
—
|
NE NERFINISHED |
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: MXF | Statement: [Interoperable Master Format, usesContainer, MXF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContainer Context triple: [Interoperable Master Format, usesContainer, MXF]
-
A.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
B.
containsUse
Indicates that one entity includes or makes use of another entity as part of its composition, function, or implementation.
-
C.
containerType
Indicates the specific kind or category of container associated with or used to hold an entity.
-
D.
containerFeature
Indicates that one entity possesses or provides a specific feature, characteristic, or capability related to a container or containment context for another entity.
-
E.
containmentStructure
Indicates that one entity serves as a physical or logical container or enclosing structure for another entity.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 29, 2026, 7:59 p.m.