Triple
T13936916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winner and Waster |
E335142
|
entity |
| Predicate | anonymousWork |
P111857
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Winner and Waster, anonymousWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anonymousWork Context triple: [Winner and Waster, anonymousWork, true]
-
A.
otherWork
Indicates that one work is related to another work by the same creator, but is distinct from the primary or referenced work.
-
B.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
C.
namedForWork
Indicates that one entity is named in honor of, or derived from the title of, a particular work (such as a book, film, artwork, or other creative production).
-
D.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
E.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
- F. None of above. chosen
Provenance (4 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0fc42c8190ada203febd57e851 |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:17 p.m.