Triple
T36543217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Diamonds |
E901074
|
entity |
| Predicate | playsRules |
P6601
|
FINISHED |
| Object | World Netball 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: World Netball rules | Statement: [Australian Diamonds, playsRules, World Netball rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRules Context triple: [Australian Diamonds, playsRules, World Netball rules]
-
A.
playedUnderRulesOf
chosen
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
B.
playfishSpecialization
Indicates a specialization relationship where an entity focuses on or is particularly adapted to playing with fish.
-
C.
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.
-
D.
typicallyPlays
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
-
E.
contestRule
Indicates that there is a rule or regulation governing how a contest is conducted or participated in.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:11 p.m.