Triple
T16686074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2 Enoch |
E405464
|
entity |
| Predicate | hasOriginalLanguageHypothesis |
P108449
|
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: [2 Enoch, hasOriginalLanguageHypothesis, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalLanguageHypothesis Context triple: [2 Enoch, hasOriginalLanguageHypothesis, Greek]
-
A.
originalLanguageHypothesis
chosen
Indicates a proposed or inferred original language in which a work, text, or expression was first created or formulated.
-
B.
languageHypothesis
Indicates a proposed or inferred relationship concerning the language used, such as a conjecture about which language applies or how language is involved in a given context.
-
C.
hasCommonOriginHypothesis
Indicates that there exists a hypothesis proposing a shared or common origin between the related entities.
-
D.
indirectOriginLanguage
Indicates that something originates from a particular language, not directly but through one or more intermediate languages or sources.
-
E.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea550c0819085bd36c44237a61a |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.