Triple
T37287513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudo-Phalaris letters tradition |
E925574
|
entity |
| Predicate | actuallyAuthoredBy |
P176163
|
FINISHED |
| Object | unknown later authors |
—
|
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 later authors | Statement: [Pseudo-Phalaris letters tradition, actuallyAuthoredBy, unknown later authors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuallyAuthoredBy Context triple: [Pseudo-Phalaris letters tradition, actuallyAuthoredBy, unknown later authors]
-
A.
authoredWith
Indicates that two or more entities jointly created or wrote a work together.
-
B.
actuallyWrittenBy
chosen
Indicates that the specified work was in fact authored by the given entity, possibly correcting or overriding a previously assumed or credited author.
-
C.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
-
D.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
E.
actualAuthorOfAssociatedText
Indicates that an entity is the real creator or writer of a given associated text, regardless of how the text is attributed elsewhere.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.