Triple
T11815748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Lockett |
E280994
|
entity |
| Predicate | recordBreakingGoalNumber |
P42667
|
FINISHED |
| Object | 1300 |
—
|
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: 1300 | Statement: [Tony Lockett, recordBreakingGoalNumber, 1300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordBreakingGoalNumber Context triple: [Tony Lockett, recordBreakingGoalNumber, 1300]
-
A.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
B.
brokeRecord
chosen
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
-
C.
totalGoalsRecord
Indicates the total number of goals that have been recorded for an entity across all relevant events or contexts.
-
D.
goalNumber
Indicates that an entity is associated with a specific target or objective quantified as a number.
-
E.
isAllTimeRecordHolderFor
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.