Triple
T23204528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Jenkins |
E580412
|
entity |
| Predicate | hasCommonShortFormOfGivenName |
P99167
|
FINISHED |
| Object | Harry as a short form of Henry |
—
|
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: Harry as a short form of Henry | Statement: [Harry Jenkins, hasCommonShortFormOfGivenName, Harry as a short form of Henry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonShortFormOfGivenName Context triple: [Harry Jenkins, hasCommonShortFormOfGivenName, Harry as a short form of Henry]
-
A.
isShortFormOfMultiNames
Indicates that one term is a shortened or abbreviated form corresponding to multiple different full names.
-
B.
commonShortNameFor
chosen
Indicates that one entity is a commonly used short or abbreviated name for another entity.
-
C.
isShortName
Indicates that one name is an abbreviated or shorter form of another name.
-
D.
hasShortLatinName
Indicates that an entity is associated with a brief or abbreviated Latin name.
-
E.
isCommonAsFirstName
Indicates that the referenced name is frequently used as a first (given) name within a specified population or context.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907c1d7c8190aca252a39ae0da86 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.