Triple
T29710242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France vs Australia |
E751758
|
entity |
| Predicate | goalsScoredByAustralia |
P74219
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [France vs Australia, goalsScoredByAustralia, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalsScoredByAustralia Context triple: [France vs Australia, goalsScoredByAustralia, 1]
-
A.
AustraliaScore
chosen
Indicates that a scoring event or point total is attributed to Australia in a given context.
-
B.
AFLGoalsScored
Indicates the number of goals a player scores in an Australian Football League (AFL) match or season.
-
C.
AllAustralianTeam
Indicates that an entity has been selected for inclusion in the All-Australian Team, representing top-level recognition in Australian rules football for a given period.
-
D.
AustraliaOvers
Indicates a relationship where one entity surpasses, exceeds, or goes beyond another in the specific context associated with Australia.
-
E.
AustraliaGroupCOpeningMatch
Indicates that an event is the opening match of Group C in a competition held in or associated with Australia.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 7:30 p.m.