Triple
T33193070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Burns |
E849664
|
entity |
| Predicate | placeOfDefeatByJackJohnson |
P73055
|
FINISHED |
| Object | Sydney, New South Wales, Australia |
—
|
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, New South Wales, Australia | Statement: [Tommy Burns, placeOfDefeatByJackJohnson, Sydney, New South Wales, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfDefeatByJackJohnson Context triple: [Tommy Burns, placeOfDefeatByJackJohnson, Sydney, New South Wales, Australia]
-
A.
fightDateWithJackJohnson
Indicates the date on which an entity had a fight with Jack Johnson.
-
B.
locationOfMajorDefeat
chosen
Indicates the place where a significant or decisive defeat of a party occurred.
-
C.
defeatedInEvent
Indicates that one entity lost to another entity in the context of a specific event or competition.
-
D.
largestDefeatOpponent
Indicates that one entity experienced its most significant loss or defeat at the hands of the specified opponent.
-
E.
finalDefeatIn
Indicates that one entity experiences its ultimate or conclusive defeat within a specified event, context, or location.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:29 a.m.