Triple
T32852985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Junior A Lacrosse League |
E840302
|
entity |
| Predicate | playsRulesVariant |
P109968
|
FINISHED |
| Object | box lacrosse rules |
—
|
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: box lacrosse rules | Statement: [Ontario Junior A Lacrosse League, playsRulesVariant, box lacrosse rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRulesVariant Context triple: [Ontario Junior A Lacrosse League, playsRulesVariant, box lacrosse rules]
-
A.
playsSevensVariant
Indicates that an entity participates in or engages in a sevens variant of a game or sport.
-
B.
playsVariantOf
chosen
Indicates that one entity performs, uses, or engages with a version or adaptation of another entity, typically differing in form, rules, or style from the original.
-
C.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
D.
hasCardGameVariant
Indicates that one game is a variation or modified form of another card game.
-
E.
hasPlayConvention
Indicates that an activity, game, or performance follows a particular rule, norm, or convention for how it is to be played or carried out.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:17 a.m.