Triple
T28401884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Platonic letters |
E719412
|
entity |
| Predicate | letterConsideredMostPossiblyAuthentic |
P100301
|
FINISHED |
| Object | Seventh Letter |
—
|
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: Seventh Letter | Statement: [Platonic letters, letterConsideredMostPossiblyAuthentic, Seventh Letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: letterConsideredMostPossiblyAuthentic Context triple: [Platonic letters, letterConsideredMostPossiblyAuthentic, Seventh Letter]
-
A.
authenticTextIn
Indicates that a given text is the authoritative or original version of a work within a specified context, source, or collection.
-
B.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
-
C.
notableLetter
chosen
Indicates that a letter associated with an entity is especially significant, famous, or otherwise noteworthy in relation to that entity.
-
D.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
E.
traditionalNumberOfAuthenticLetters
Indicates the conventionally recognized count of letters considered authentic within a specified collection or corpus.
- 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.