Triple
T5734942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evan |
E126478
|
entity |
| Predicate | hasMeaningSource |
P8506
|
FINISHED |
| Object | Hebrew YHWH chanan |
—
|
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 YHWH chanan | Statement: [Evan, hasMeaningSource, Hebrew YHWH chanan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningSource Context triple: [Evan, hasMeaningSource, Hebrew YHWH chanan]
-
A.
sourceLanguageMeaning
chosen
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
B.
hasMeaningViaJohn
Indicates that something possesses or conveys its meaning specifically through John as the interpretive or mediating agent.
-
C.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
-
D.
hasMean
Indicates that one entity possesses, exhibits, or is characterized by a particular mean value or average.
-
E.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.