Triple
T33354255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocalypse |
E854027
|
entity |
| Predicate | etymologyFromGreekWord |
P30589
|
FINISHED |
| Object | apokalypsis |
—
|
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: apokalypsis | Statement: [Apocalypse, etymologyFromGreekWord, apokalypsis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyFromGreekWord Context triple: [Apocalypse, etymologyFromGreekWord, apokalypsis]
-
A.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
-
B.
etymologyGloss
Indicates that a term’s meaning is explained by a brief gloss specifically describing its etymological origin or source.
-
C.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
D.
etymologyContext
Indicates the contextual or situational background (such as time, place, culture, or domain) relevant to the origin and historical development of a word or term.
-
E.
etymologyRelatesTo
chosen
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:34 a.m.