Triple
T32485987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayim |
E830241
|
entity |
| Predicate | isAlsoHebrewCommonNounFor |
P57944
|
FINISHED |
| Object | water |
—
|
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: water | Statement: [Mayim, isAlsoHebrewCommonNounFor, water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlsoHebrewCommonNounFor Context triple: [Mayim, isAlsoHebrewCommonNounFor, water]
-
A.
isAlsoCommonNounInLanguage
chosen
Indicates that an entity is also used as a common noun in a specified language.
-
B.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
C.
correspondsToInHebrew
Indicates that one entity is the Hebrew-language equivalent or counterpart of another entity.
-
D.
hasSingularHebrewForm
Indicates that an entity has a corresponding singular form in the Hebrew language.
-
E.
oftenRenderedFromHebrewTerm
Indicates that one term is frequently used as the translation or rendering of a corresponding term originating from Hebrew.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3f834c481909c129c8739168d34 |
completed | May 3, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:58 a.m.