Triple
T34781503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | More Mishaps |
E1002673
|
entity |
| Predicate | hasAuthorConnectionTo |
P193082
|
FINISHED |
| Object | Allen Ginsberg |
—
|
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: Allen Ginsberg | Statement: [More Mishaps, hasAuthorConnectionTo, Allen Ginsberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorConnectionTo Context triple: [More Mishaps, hasAuthorConnectionTo, Allen Ginsberg]
-
A.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
B.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
C.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
D.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
-
E.
hasAuthorRoleFor
Indicates that an entity serves in the role of author for another entity, such as a work, document, or publication.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 3:59 p.m.