Triple
T28401883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Platonic letters |
E719412
|
entity |
| Predicate | scholarlyConsensusOnAuthenticity |
P81491
|
FINISHED |
| Object | mostly spurious |
—
|
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: mostly spurious | Statement: [Platonic letters, scholarlyConsensusOnAuthenticity, mostly spurious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyConsensusOnAuthenticity Context triple: [Platonic letters, scholarlyConsensusOnAuthenticity, mostly spurious]
-
A.
includesWorksOfDisputedAuthenticity
chosen
Indicates that the subject contains or incorporates works whose authenticity is uncertain or contested.
-
B.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
-
C.
scholarlyConsensusOnIdentity
Indicates that there is a prevailing agreement among scholars regarding the identity or identification of a particular entity.
-
D.
authorshipEvidence
Indicates evidence or justification supporting a claim that one entity is the author or creator of another.
-
E.
historicAuthenticity
Indicates that something accurately reflects or preserves the genuine characteristics, context, and conditions of its historical period.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d6c02748190b9d55772ca72e979 |
completed | May 2, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:20 a.m.