Triple
T34992871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Melbourne/Sydney Swans |
E1009440
|
entity |
| Predicate | SydneyRival |
P22658
|
FINISHED |
| Object | Greater Western Sydney Giants |
—
|
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: Greater Western Sydney Giants | Statement: [South Melbourne/Sydney Swans, SydneyRival, Greater Western Sydney Giants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SydneyRival Context triple: [South Melbourne/Sydney Swans, SydneyRival, Greater Western Sydney Giants]
-
A.
rivalOf
chosen
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
rivalryInvolvesCity
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
C.
rivalNickname
Indicates that one entity uses or is known by a nickname specifically in the context of rivalry with another entity.
-
D.
nicknameOfNSWTeam
Indicates that one entity is used as a nickname for a New South Wales (NSW) sports team.
-
E.
countryOfRivalry
Indicates that one entity is a country with which another entity has a relationship of rivalry or adversarial competition.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.