Triple
T33761956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humph |
E865130
|
entity |
| Predicate | hasAbbreviationRelationTo |
P45686
|
FINISHED |
| Object | Humphrey |
—
|
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: Humphrey | Statement: [Humph, hasAbbreviationRelationTo, Humphrey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationRelationTo Context triple: [Humph, hasAbbreviationRelationTo, Humphrey]
-
A.
usesAbbreviationOf
Indicates that one entity employs a shortened or abbreviated form of the name or designation of another entity.
-
B.
hasAbbreviationOrForm
Indicates that one entity serves as an abbreviation, shortened form, or alternative written form of another entity.
-
C.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
-
D.
alternativeAbbreviation
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
E.
isAbbreviation
chosen
Indicates that one term is a shortened or abbreviated form of another term.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.