Triple
T8761713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans-Jürgen |
E208215
|
entity |
| Predicate | shortFormOfComponent |
P83434
|
FINISHED |
| Object | Hans is a short form of Johannes |
—
|
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: Hans is a short form of Johannes | Statement: [Hans-Jürgen, shortFormOfComponent, Hans is a short form of Johannes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortFormOfComponent Context triple: [Hans-Jürgen, shortFormOfComponent, Hans is a short form of Johannes]
-
A.
shortFormType
chosen
Indicates that one entity is a shortened, abbreviated, or otherwise condensed form or variant of another entity.
-
B.
shortCodeType
Indicates that one entity is classified as a specific type or category of short code associated with another entity.
-
C.
shortNameInJapanese
Indicates that an entity has a specific abbreviated or shorter form of its name expressed in the Japanese language.
-
D.
bearerShortName
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
-
E.
isShort
Indicates that one entity has a relatively small height, length, or duration compared to a standard or to other entities.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfa9d6c81908c4c6b3a6f84f67d |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.