Triple
T37163898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VobSub |
E920744
|
entity |
| Predicate | canBeMuxedInto |
P60771
|
FINISHED |
| Object | Matroska files |
—
|
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: Matroska files | Statement: [VobSub, canBeMuxedInto, Matroska files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMuxedInto Context triple: [VobSub, canBeMuxedInto, Matroska files]
-
A.
hasMultiplex
Indicates that one entity possesses or is associated with multiple instances or channels of another entity within a shared structure or system.
-
B.
canMerge
chosen
Indicates that two or more entities are compatible in such a way that they can be combined into a single unified entity or structure.
-
C.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
-
D.
canBeMultiple
Indicates that the related item, value, or association is allowed to occur more than once rather than being restricted to a single instance.
-
E.
canBeSplitAmong
Indicates that something is divisible into parts that can be distributed among multiple recipients or groups.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:15 p.m.