Triple
T2661402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | חַוָּה |
E54732
|
entity |
| Predicate | hasNameMeaningTraditionally |
P1966
|
FINISHED |
| Object | mother of all living |
—
|
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: mother of all living | Statement: [חַוָּה, hasNameMeaningTraditionally, mother of all living]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameMeaningTraditionally Context triple: [חַוָּה, hasNameMeaningTraditionally, mother of all living]
-
A.
hasGivenNameMeaning
Indicates that a given name carries a particular meaning or semantic interpretation.
-
B.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
C.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
D.
codeNameMeaning
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
-
E.
meaningOfNativeName
chosen
Indicates that one entity specifies the semantic meaning or translation of another entity’s native-language name.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.