Triple
T14023917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Complutensian Polyglot Bible |
E337405
|
entity |
| Predicate | NewTestamentLanguages |
P11802
|
FINISHED |
| Object | Greek |
—
|
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 | Statement: [Complutensian Polyglot Bible, NewTestamentLanguages, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NewTestamentLanguages Context triple: [Complutensian Polyglot Bible, NewTestamentLanguages, Greek]
-
A.
hasNewTestamentSourceLanguage
chosen
Indicates that something (such as a text, translation, or reference) is associated with a particular source language of the New Testament.
-
B.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
C.
sharesNewTestamentCanonWith
Indicates that two entities recognize and use the same set of New Testament canonical books.
-
D.
numberOfNewTestamentBooks
Indicates the total count of books contained in the New Testament.
-
E.
usedScriptureTranslation
Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.