Triple
T23054533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hecht |
E574115
|
entity |
| Predicate | hasMeaningInGerman |
P56110
|
FINISHED |
| Object | pike (fish) |
—
|
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: pike (fish) | Statement: [Hecht, hasMeaningInGerman, pike (fish)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningInGerman Context triple: [Hecht, hasMeaningInGerman, pike (fish)]
-
A.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
B.
meaningInGerman
chosen
Indicates that one entity expresses the meaning or translation of another entity in the German language.
-
C.
hasMeaningInEstonian
Indicates that something possesses a particular meaning or interpretation in the Estonian language.
-
D.
hasMeaningInJapanese
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Japanese language.
-
E.
hasMeaningInChinese
Indicates that one entity (such as a word, phrase, or symbol) possesses a specific meaning or interpretation within the Chinese language.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867eaed0819095c7da6b06101b12 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.