Triple
T24928749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorenson Video |
E618930
|
entity |
| Predicate | encodingSoftware |
P82559
|
FINISHED |
| Object | Sorenson Squeeze |
—
|
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: Sorenson Squeeze | Statement: [Sorenson Video, encodingSoftware, Sorenson Squeeze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingSoftware Context triple: [Sorenson Video, encodingSoftware, Sorenson Squeeze]
-
A.
encodingLibrary
chosen
Indicates that one entity is the software library or tool used to encode, transform, or serialize the other entity’s data or content.
-
B.
developedSoftware
Indicates that one entity created, programmed, or significantly contributed to the creation of a particular software system or application for another entity or purpose.
-
C.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
D.
softwareFor
Indicates that one entity is designed, intended, or used to operate on, support, or be compatible with another entity as software.
-
E.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:29 a.m.