Triple
T4704048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samu |
E104345
|
entity |
| Predicate | meaningInOriginLanguage |
P14723
|
FINISHED |
| Object | "name of God" (via Samuel) |
—
|
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: "name of God" (via Samuel) | Statement: [Samu, meaningInOriginLanguage, "name of God" (via Samuel)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningInOriginLanguage Context triple: [Samu, meaningInOriginLanguage, "name of God" (via Samuel)]
-
A.
etymologicalRootMeaning
chosen
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
B.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
C.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
D.
meaningInGerman
Indicates that one entity expresses the meaning or translation of another entity in the German language.
-
E.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.