Triple
T30108099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts and Catholic Epistles in Byzantine textform |
E765185
|
entity |
| Predicate | basedOnTextType |
P93688
|
FINISHED |
| Object | Byzantine textform |
—
|
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 textform | Statement: [Acts and Catholic Epistles in Byzantine textform, basedOnTextType, Byzantine textform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnTextType Context triple: [Acts and Catholic Epistles in Byzantine textform, basedOnTextType, Byzantine textform]
-
A.
basedOnText
Indicates that something is derived, adapted, or developed from a specific text source.
-
B.
basedOnType
chosen
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
C.
textType
Indicates the classification of a text according to its type, format, or genre.
-
D.
textTypePreferred
Indicates that one entity has a preferred or favored type or category of text in relation to another entity.
-
E.
basedOnMedium
Indicates that one entity is derived from, adapted from, or created using another entity as its source medium or foundational material.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 29, 2026, 7:10 p.m.