Triple
T28992936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quilters Hall of Fame |
E736074
|
entity |
| Predicate | hasHonoreeType |
P4123
|
FINISHED |
| Object | quilt designer |
—
|
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: quilt designer | Statement: [Quilters Hall of Fame, hasHonoreeType, quilt designer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonoreeType Context triple: [Quilters Hall of Fame, hasHonoreeType, quilt designer]
-
A.
hasHonorificType
Indicates that an entity is associated with a specific type or category of honorific title or form of address.
-
B.
honoreeEligibility
Indicates that an entity meets the required conditions or qualifications to be selected or recognized as an honoree.
-
C.
hasNomineeType
Indicates that an entity has a nominee belonging to a specified type or category.
-
D.
hasHonoraryMember
Indicates that an entity is recognized as an honorary (non-regular) member of another entity, typically without full rights or obligations of standard membership.
-
E.
honourType
chosen
Indicates the specific category or classification of an honour or award associated with an entity.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 9:28 a.m.