Triple
T37481532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crufts |
E931424
|
entity |
| Predicate | eligibilityControlledBy |
P18203
|
FINISHED |
| Object | The Kennel Club |
—
|
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: The Kennel Club | Statement: [Crufts, eligibilityControlledBy, The Kennel Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityControlledBy Context triple: [Crufts, eligibilityControlledBy, The Kennel Club]
-
A.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
B.
eligibilityContext
Indicates the situational or conditional factors under which an entity qualifies for or is considered eligible for something.
-
C.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
eligibilityUnit
chosen
Indicates that one entity serves as the unit or basis used to determine another entity’s eligibility for a benefit, status, or condition.
-
E.
eligibilityArea
Indicates that a specified geographic or conceptual area defines where something (such as a person, item, or activity) is eligible or permitted.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.