Triple
T30138784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauline Epistles in Byzantine textform |
E766069
|
entity |
| Predicate | followsTextType |
P5468
|
FINISHED |
| Object | Byzantine text-type |
—
|
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: Byzantine text-type | Statement: [Pauline Epistles in Byzantine textform, followsTextType, Byzantine text-type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsTextType Context triple: [Pauline Epistles in Byzantine textform, followsTextType, Byzantine text-type]
-
A.
followsInText
Indicates that one textual element appears immediately or subsequently after another within the same text.
-
B.
followsCharacterType
Indicates that one character’s behavior, role, or traits are patterned after, derived from, or constrained by a specified character type.
-
C.
followsElementType
Indicates that one element type comes directly after another element type in a defined order or sequence.
-
D.
textType
chosen
Indicates the classification of a text according to its type, format, or genre.
-
E.
followsLetter
Indicates that one element in a sequence comes immediately after another element in alphabetical or ordered letter arrangement.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 29, 2026, 7:17 p.m.