Triple
T25855098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bendigo Spirit |
E651320
|
entity |
| Predicate | hasHomeCountryTeamStatus |
P118303
|
FINISHED |
| Object | Australian team |
—
|
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: Australian team | Statement: [Bendigo Spirit, hasHomeCountryTeamStatus, Australian team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCountryTeamStatus Context triple: [Bendigo Spirit, hasHomeCountryTeamStatus, Australian team]
-
A.
hasHomeTeamCountry
Indicates that an entity representing a sports match or event is associated with the country of its designated home team.
-
B.
homeCountryTeamStatus
chosen
Indicates the relationship between an entity and a country’s team, specifying whether that team is considered the entity’s home or primary national team.
-
C.
hasHomeTeamLeagueCountry
Indicates that the country specified is the country in which the league of the home team is based.
-
D.
hasHomeCountryLeague
Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
-
E.
homeCountryTeamOf
Indicates that one entity is the national team representing the home country of another entity.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 22, 2026, 8 a.m.