Triple
T15290040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hel |
E365501
|
entity |
| Predicate | hasModernCognate |
P2525
|
FINISHED |
| Object | English word hell |
—
|
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: English word hell | Statement: [Hel, hasModernCognate, English word hell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernCognate Context triple: [Hel, hasModernCognate, English word hell]
-
A.
hasCognate
chosen
Indicates that two linguistic forms in different languages share a common historical origin, typically descending from the same ancestral word.
-
B.
cognateOf
Indicates that two linguistic forms share a common historical origin, typically descending from the same ancestral word.
-
C.
hasModernNameLanguage
Indicates that the modern name of an entity is expressed in a particular language.
-
D.
modernLanguageDescendant
Indicates that one language is a direct or indirect descendant of another language in the modern era.
-
E.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e5635b4819092a69b5806d15bff |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.