Triple
T28619769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DivX |
E724351
|
entity |
| Predicate | hasFormerDeveloper |
P85947
|
FINISHED |
| Object | DivXNetworks, Inc. |
—
|
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: DivXNetworks, Inc. | Statement: [DivX, hasFormerDeveloper, DivXNetworks, Inc.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerDeveloper Context triple: [DivX, hasFormerDeveloper, DivXNetworks, Inc.]
-
A.
formerlyDevelopedBy
chosen
Indicates that an entity was developed in the past by another entity, but is no longer developed by that same party.
-
B.
formerDeveloper
Indicates that an entity previously worked as a developer for another entity but no longer holds that role.
-
C.
hasFormerFounder
Indicates that an entity was previously a founder of another entity but no longer holds that founder role or status.
-
D.
laterDeveloper
Indicates that one developer’s work, role, or involvement occurs after another developer in time.
-
E.
hasFounderOfDeveloper
Indicates that an entity has as its founder a specific developer who established or created it.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 4:32 a.m.