Triple
T2366110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskegon Lumberjacks (hockey) |
E47382
|
entity |
| Predicate | usesPlayerStatus |
P22493
|
FINISHED |
| Object | amateur |
—
|
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: amateur | Statement: [Muskegon Lumberjacks (hockey), usesPlayerStatus, amateur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlayerStatus Context triple: [Muskegon Lumberjacks (hockey), usesPlayerStatus, amateur]
-
A.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
B.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
C.
hasSportsStatus
chosen
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
D.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
E.
player
Indicates that an entity participates in a game, sport, or activity in the role of a player.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc749f8e0819094144b9dd9db8790 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.