Triple
T33238615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian rugby league |
E850902
|
entity |
| Predicate | hasClubBase |
P193204
|
FINISHED |
| Object | Sydney |
—
|
NE NERFINISHED |
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: Sydney | Statement: [Australian rugby league, hasClubBase, Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubBase Context triple: [Australian rugby league, hasClubBase, Sydney]
-
A.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
B.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
C.
hasClubName
Indicates that an entity is associated with or identified by a specific club name.
-
D.
hasPlayersClub
Indicates that an entity operates, sponsors, or is associated with a players’ club or loyalty program for players.
-
E.
isTraditionalClubIn
Indicates that a club is traditionally associated with or located in a particular place or region.
- F. None of above. chosen
Provenance (4 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: May 1, 2026, 1:31 a.m.