Triple
T21012967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirom |
E517596
|
entity |
| Predicate | isLinguisticVariantIn |
P34737
|
FINISHED |
| Object | Hebrew-derived names |
—
|
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-derived names | Statement: [Hirom, isLinguisticVariantIn, Hebrew-derived names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinguisticVariantIn Context triple: [Hirom, isLinguisticVariantIn, Hebrew-derived names]
-
A.
linguisticVariant
chosen
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
B.
hasLinguisticVariationType
Indicates that one linguistic form is related to another by a specific type of variation, such as dialectal, orthographic, morphological, or phonological difference.
-
C.
hasLinguisticVariety
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
D.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
E.
labelLanguageVariant
Indicates that one label is a language-specific variant or localized form of another label.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc41d57881908b9ab17d1844a8d0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.