Triple
T25811060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EnterMedia |
E650110
|
entity |
| Predicate | originalNetworkForNotableWork |
P120334
|
FINISHED |
| Object | KBS2 |
—
|
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: KBS2 | Statement: [EnterMedia, originalNetworkForNotableWork, KBS2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkForNotableWork Context triple: [EnterMedia, originalNetworkForNotableWork, KBS2]
-
A.
networkOfNotableWork
Indicates that one entity is a network, collection, or system associated with the creation, distribution, or context of another entity’s notable work.
-
B.
originalNetworkOfProducedWork
chosen
Indicates the network or distribution platform on which a produced work was originally released or made available.
-
C.
networkOfOriginalWork
Indicates that one work is part of, or derived from, the same underlying original work as another within a shared network of related creations.
-
D.
networkOfWorkAppearedIn
Indicates that a work is part of, or appears within, a particular network or collection of related works.
-
E.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 22, 2026, 7:10 a.m.