Triple
T29026912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V. Lebhaft |
E737616
|
entity |
| Predicate | hasParentWorkNickname |
P101523
|
FINISHED |
| Object | Rhenish |
—
|
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: Rhenish | Statement: [V. Lebhaft, hasParentWorkNickname, Rhenish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentWorkNickname Context triple: [V. Lebhaft, hasParentWorkNickname, Rhenish]
-
A.
hasParentWork
Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
-
B.
hasFullNameInWork
Indicates that an entity is referred to by a specific full name within a particular work or publication.
-
C.
associatedNicknameOfWork
chosen
Indicates that a given nickname or informal title is commonly used to refer to a particular work.
-
D.
hasParentWorkKey
Indicates that an entity is associated with the identifier (key) of the parent work from which it is derived or of which it is a part.
-
E.
hasGivenNameInWork
Indicates that a work specifies or uses a particular given (first) name for an entity or character.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 28, 2026, 9:53 a.m.