Triple
T37163901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VobSub |
E920744
|
entity |
| Predicate | commonlyUsedWithTool |
P120710
|
FINISHED |
| Object | VirtualDub |
—
|
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: VirtualDub | Statement: [VobSub, commonlyUsedWithTool, VirtualDub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsedWithTool Context triple: [VobSub, commonlyUsedWithTool, VirtualDub]
-
A.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
C.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
D.
usedInCollaborationWith
Indicates that an entity is employed, applied, or utilized together with another entity as part of a joint or cooperative activity.
-
E.
notablyUsedWith
chosen
Indicates that one entity is commonly or prominently used together with another entity, in a way that is especially characteristic or noteworthy.
- 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_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:15 p.m.