Triple
T22110929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHL Priority Selection |
E546415
|
entity |
| Predicate | playerStatusAfterSelection |
P13375
|
FINISHED |
| Object | OHL-drafted prospect |
—
|
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: OHL-drafted prospect | Statement: [OHL Priority Selection, playerStatusAfterSelection, OHL-drafted prospect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerStatusAfterSelection Context triple: [OHL Priority Selection, playerStatusAfterSelection, OHL-drafted prospect]
-
A.
playerStatus
chosen
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
-
B.
playerOutcome
Indicates the result or consequence experienced by a player in a game, match, or scenario (such as winning, losing, or drawing).
-
C.
participantStatus
Indicates the role, condition, or level of involvement that a participant has within a specific event, process, or relationship.
-
D.
regulatesPlayerSelection
Indicates that an entity sets or enforces rules or constraints governing how players are chosen or selected.
-
E.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12949cc7881908898ca7dc130f57f |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.