Triple
T25550358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSH |
E640422
|
entity |
| Predicate | hasGenderedVariant |
P48671
|
FINISHED |
| Object | H.S.H. (punctuated form) |
—
|
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: H.S.H. (punctuated form) | Statement: [HSH, hasGenderedVariant, H.S.H. (punctuated form)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderedVariant Context triple: [HSH, hasGenderedVariant, H.S.H. (punctuated form)]
-
A.
hasGenderVariant
chosen
Indicates that one entity is a gender-specific form or variant of another entity.
-
B.
hasAlternativeGenderUsage
Indicates that an entity is used with a different or non-standard gender form in certain contexts or usages.
-
C.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
-
D.
hasGenderedFormOrigin
Indicates that one form of an entity originates from or is derived based on a specific grammatical or social gender.
-
E.
hasGenderFormat
Indicates that something is associated with or expressed in a particular gender-related format or representation.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 3:36 p.m.