Triple
T7247111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Epistle to James Smith |
E156499
|
entity |
| Predicate | hasEpistolaryForm |
P6480
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Epistle to James Smith, hasEpistolaryForm, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpistolaryForm Context triple: [The Epistle to James Smith, hasEpistolaryForm, true]
-
A.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
lettersWrittenBetween
Indicates that letters have been written and exchanged between the two entities, reflecting a mutual correspondence.
-
C.
hasWrittenForm
Indicates that an entity is associated with a specific written or textual representation.
-
D.
hasDiplomaticFormat
Indicates that a diplomatic communication, document, or interaction follows a specific recognized diplomatic format or protocol.
-
E.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea749fb08190841c0aa8c5bd0727 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.