Triple
T19077927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sodom |
E466950
|
entity |
| Predicate | etymologyClaim |
P453
|
FINISHED |
| Object | possibly related to Hebrew root for burning |
—
|
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: possibly related to Hebrew root for burning | Statement: [Sodom, etymologyClaim, possibly related to Hebrew root for burning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyClaim Context triple: [Sodom, etymologyClaim, possibly related to Hebrew root for burning]
-
A.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
B.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
C.
etymologyReason
Indicates the reason, source, or origin explaining how or why a term acquired its particular etymology.
-
D.
etymology
chosen
Indicates the historical origin and development of a word or term, including its source language and form.
-
E.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e61b60819092d42614f04a087c |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.