Triple
T25997195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Dyer Medal |
E646516
|
entity |
| Predicate | clubLegendHonoured |
P15254
|
FINISHED |
| Object | Jack Dyer |
—
|
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: Jack Dyer | Statement: [Jack Dyer Medal, clubLegendHonoured, Jack Dyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubLegendHonoured Context triple: [Jack Dyer Medal, clubLegendHonoured, Jack Dyer]
-
A.
clubLegendOf
chosen
Indicates that a person is widely regarded as a legendary or iconic figure for a particular club, typically due to exceptional contribution or long-term impact.
-
B.
clubHonour
Indicates that a club has received or been awarded a particular honour, title, or distinction.
-
C.
honoursAsPlayer
Indicates that one entity has received awards, recognitions, or honours specifically for their role or achievements as a player.
-
D.
namedAfterHallOfFame
Indicates that one entity is named in honor of, or after, a Hall of Fame or a Hall of Fame inductee.
-
E.
hallOfFameAssociation
Indicates that an entity is formally associated with a hall of fame, such as through induction, nomination, or recognition.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057012248190a486e723fdd2107e |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:58 a.m.