Triple
T5373381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protestant Bible |
E108903
|
entity |
| Predicate | languageOfEarliestTexts |
P3926
|
FINISHED |
| Object | Hebrew |
—
|
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: Hebrew | Statement: [Protestant Bible, languageOfEarliestTexts, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfEarliestTexts Context triple: [Protestant Bible, languageOfEarliestTexts, Hebrew]
-
A.
earliestTextsIn
Indicates that certain texts are among the earliest known examples found in or associated with a particular place or context.
-
B.
languageOfEarliestForm
chosen
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
C.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
D.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
E.
hasWritingTraditionSince
Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.