Triple
T4603997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on Matthew |
E100385
|
entity |
| Predicate | originallyWrittenIn |
P5459
|
FINISHED |
| Object | Greek language |
—
|
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: Greek language | Statement: [Commentary on Matthew, originallyWrittenIn, Greek language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyWrittenIn Context triple: [Commentary on Matthew, originallyWrittenIn, Greek language]
-
A.
originallyWrittenFor
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
B.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
C.
alsoWrittenIn
Indicates that the same content, work, or information is expressed or available in an additional language, script, or writing system.
-
D.
originalTextLanguage
chosen
Indicates the language in which a text was originally written or created before any translation or adaptation.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5975ec688190839bd22669343a76 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.