Triple
T35000116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William S. Burroughs bibliography |
E1009648
|
entity |
| Predicate | includesNotableCollaborationWith |
P8554
|
FINISHED |
| Object | Brion Gysin |
E715369
|
NE 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: Brion Gysin | Statement: [William S. Burroughs bibliography, includesNotableCollaborationWith, Brion Gysin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNotableCollaborationWith Context triple: [William S. Burroughs bibliography, includesNotableCollaborationWith, Brion Gysin]
-
A.
notableCollaboration
chosen
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
B.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
-
C.
hasNotableCollaborationPattern
Indicates that there is a recognizable, significant way in which collaborations typically occur between the entities.
-
D.
hasNotableCollaborationInField
Indicates a collaborative relationship between entities that is recognized as particularly significant or influential within a specific field or domain.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- F. None of above.
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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b28fc3fc8190a897949f7f673539 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.