Triple
T30888286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrie |
E786825
|
entity |
| Predicate | hasDiminutiveOrVariantRelation |
P456
|
FINISHED |
| Object | Hendry |
—
|
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: Hendry | Statement: [Hendrie, hasDiminutiveOrVariantRelation, Hendry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiminutiveOrVariantRelation Context triple: [Hendrie, hasDiminutiveOrVariantRelation, Hendry]
-
A.
hasDiminutive
chosen
Indicates that one entity is a diminutive form or smaller/affectionate variant of another entity.
-
B.
isShortenedVariantOf
Indicates that one form of an expression is a shortened or abbreviated version of another, longer form.
-
C.
hasOnomasticRelation
Indicates that there is a relationship between entities based on names, naming patterns, or shared onomastic (name-related) features.
-
D.
isReducedFormOf
Indicates that one entity is a simplified or more compact version derived from another entity while preserving its essential meaning or structure.
-
E.
isSometimesUsedAsVariantOf
Indicates that one entity is occasionally employed as an alternative or substitute form of another entity, but not as its primary or standard version.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 29, 2026, 8:49 p.m.