Triple
T15375243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illawarra Hawks |
E367649
|
entity |
| Predicate | hasRivalryInLeague |
P74502
|
FINISHED |
| Object | other NBL clubs |
—
|
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: other NBL clubs | Statement: [Illawarra Hawks, hasRivalryInLeague, other NBL clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryInLeague Context triple: [Illawarra Hawks, hasRivalryInLeague, other NBL clubs]
-
A.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
B.
hasHomeStadiumInRivalry
Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
-
C.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
D.
associatedRivalry
chosen
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
E.
hasRivalrySeries
Indicates a recurring competitive relationship or series of contests held between two entities.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5d6f808190b0a4cdb35dc89e69 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.