Triple
T21012965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirom |
E517596
|
entity |
| Predicate | isEtymologicallyLinkedTo |
P30589
|
FINISHED |
| Object | ancient Hebrew culture |
—
|
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: ancient Hebrew culture | Statement: [Hirom, isEtymologicallyLinkedTo, ancient Hebrew culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEtymologicallyLinkedTo Context triple: [Hirom, isEtymologicallyLinkedTo, ancient Hebrew culture]
-
A.
hasEtymologicalBasis
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
-
B.
etymologyRelatesTo
chosen
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
C.
hasEtymologyConcept
Indicates that something derives its origin, form, or meaning from a particular etymological concept or source.
-
D.
sharesEtymologyWith
Indicates that two terms originate from the same linguistic root or source word, or have closely related historical word origins.
-
E.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
- 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.