Triple
T32852995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Junior A Lacrosse League |
E840302
|
entity |
| Predicate | hasPlayerStatus |
P13375
|
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: [Ontario Junior A Lacrosse League, hasPlayerStatus, amateur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayerStatus Context triple: [Ontario Junior A Lacrosse League, hasPlayerStatus, amateur]
-
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.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
C.
hasPlayerCount
Indicates the number of players associated with or participating in a given entity or activity.
-
D.
inGameStatus
Indicates the current state or condition of an entity within the context of a game (e.g., active, paused, eliminated).
-
E.
hasPlayerColor
Indicates that an entity (such as a player or game piece) is associated with a specific color used to represent it.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:17 a.m.