Triple
T23624837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenneth Regan |
E583432
|
entity |
| Predicate | coauthorOfBlog |
P2389
|
FINISHED |
| Object | Gödel’s Lost Letter and P=NP |
—
|
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: Gödel’s Lost Letter and P=NP | Statement: [Kenneth Regan, coauthorOfBlog, Gödel’s Lost Letter and P=NP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coauthorOfBlog Context triple: [Kenneth Regan, coauthorOfBlog, Gödel’s Lost Letter and P=NP]
-
A.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
B.
hasCoauthor
chosen
Indicates that two or more entities have jointly authored the same work or publication.
-
C.
coAuthorshipType
Indicates the specific nature or category of the collaborative authorship relationship between two or more contributors.
-
D.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
-
E.
coAuthorAttributionTradition
Indicates that there is a recognized tradition or convention of attributing co-authorship between the related entities.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.