Triple
T30090117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malcolm Blight |
E764705
|
entity |
| Predicate | kickedGoalAfterSiren |
P168440
|
FINISHED |
| Object | famous long goal for North Melbourne |
—
|
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: famous long goal for North Melbourne | Statement: [Malcolm Blight, kickedGoalAfterSiren, famous long goal for North Melbourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kickedGoalAfterSiren Context triple: [Malcolm Blight, kickedGoalAfterSiren, famous long goal for North Melbourne]
-
A.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
-
B.
penaltyScoredBy
Indicates that a penalty (typically in a game or sport) was successfully converted or scored by a particular participant.
-
C.
goalsInExtraTime
Indicates that the related entity scored goals specifically during the extra time period of a match, beyond regular playing time.
-
D.
penaltyShootoutOccurred
Indicates that a penalty shootout took place to decide the outcome of a match or contest.
-
E.
penaltyShootoutWinner
Indicates that one competitor or team is the winner of a match decided by a penalty shootout.
- F. None of above. chosen
Provenance (4 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d6fa458819091cefc882a9b6fa3 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:05 p.m.