Triple
T27326473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Weber |
E689662
|
entity |
| Predicate | occupationalOriginLanguage |
P1754
|
FINISHED |
| Object | Middle High German |
—
|
NE NERFINISHED |
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: Middle High German | Statement: [Hans Weber, occupationalOriginLanguage, Middle High German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationalOriginLanguage Context triple: [Hans Weber, occupationalOriginLanguage, Middle High German]
-
A.
primaryLanguageInWork
Indicates that a specified language is the main or predominant language used within a particular work (such as a book, film, or document).
-
B.
isOccupationalInOrigin
Indicates that something (typically a name or term) originates from or is derived from an occupation or profession.
-
C.
lenguaDeTrabajo
Indicates that something functions as a working language used for communication in a specific context or setting.
-
D.
hasLanguageOfOrigin
chosen
Indicates that one entity has its origin or source in the language specified by another entity.
-
E.
workLanguageVariant
Indicates that one language variant of a work is related to another version of the same work, typically differing by language or localization.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 11:36 a.m.