Triple
T12037343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chavah |
E286574
|
entity |
| Predicate | nameElementRelatedTo |
P3889
|
FINISHED |
| Object | Hebrew root for life |
—
|
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 root for life | Statement: [Chavah, nameElementRelatedTo, Hebrew root for life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameElementRelatedTo Context triple: [Chavah, nameElementRelatedTo, Hebrew root for life]
-
A.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
B.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
C.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
-
D.
isRelatedName
chosen
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
E.
relatedNamedEntity
Indicates that two entities are connected through a shared or associated proper name (e.g., person, organization, location, or other named entity).
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.