Triple
T36598655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addai (pseudonymous authorship) |
E902864
|
entity |
| Predicate | actualAuthorOfAssociatedText |
P186063
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Addai (pseudonymous authorship), actualAuthorOfAssociatedText, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualAuthorOfAssociatedText Context triple: [Addai (pseudonymous authorship), actualAuthorOfAssociatedText, unknown]
-
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.
authorOfProgrammaticText
Indicates that one entity is the creator or writer of a specific programmatic text, such as source code or other machine-executable written material.
-
C.
authoredWith
Indicates that two or more entities jointly created or wrote a work together.
-
D.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
E.
hasAuthorOf
Indicates that one entity is the author or creator of 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.