Triple
T37985337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Lockett |
E947670
|
entity |
| Predicate | kickedMoreThan |
P189825
|
FINISHED |
| Object | 100 goals in multiple seasons |
—
|
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: 100 goals in multiple seasons | Statement: [Tony Lockett, kickedMoreThan, 100 goals in multiple seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kickedMoreThan Context triple: [Tony Lockett, kickedMoreThan, 100 goals in multiple seasons]
-
A.
blockedKicks
Indicates that one entity prevents or stops another entity’s kick from reaching its intended target.
-
B.
kickingAllowed
Indicates that performing or engaging in kicking is permitted within the specified context or under the given conditions.
-
C.
wasExpelledBy
Indicates that one entity was formally removed or dismissed from a group, institution, or place by another entity with the authority to do so.
-
D.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
E.
kickingTeam
Indicates which team is performing the kick in a play or event.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.