Triple
T33655746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OakSmash |
E862215
|
entity |
| Predicate | associatedWorkOfOwner |
—
|
GENERATED |
| Object | "Hamilton" (Broadway musical) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkOfOwner Context triple: [OakSmash, associatedWorkOfOwner, "Hamilton" (Broadway musical)]
-
A.
associatedWork
chosen
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
B.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
-
C.
associatedWithInWork
Indicates that two entities are connected or related to each other within the context of a particular work or project.
-
D.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
E.
relatedWorkOfPerson
Indicates that a work (such as a publication, project, or creation) is associated with or produced by a particular person.
- F. None of above.
Provenance (1 batch)
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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.