Triple
T27791192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie Marshall Award |
E701082
|
entity |
| Predicate | namedAfterLeagueRole |
P117536
|
FINISHED |
| Object | all-time AHL goals leader |
—
|
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: all-time AHL goals leader | Statement: [Willie Marshall Award, namedAfterLeagueRole, all-time AHL goals leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterLeagueRole Context triple: [Willie Marshall Award, namedAfterLeagueRole, all-time AHL goals leader]
-
A.
namedAfterLeague
Indicates that one entity has been given a name derived from or in honor of a particular league.
-
B.
namedAfterOccupationOrRole
chosen
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
-
C.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
D.
leagueSystemRole
Indicates the specific role or function an entity holds within a league’s organizational or competitive system.
-
E.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 5:28 p.m.