Triple
T6946300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL premiership cup |
E160806
|
entity |
| Predicate | previousForm |
P49038
|
FINISHED |
| Object | VFL premiership trophy |
—
|
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: VFL premiership trophy | Statement: [AFL premiership cup, previousForm, VFL premiership trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousForm Context triple: [AFL premiership cup, previousForm, VFL premiership trophy]
-
A.
subsequentForm
Indicates that one form, version, or state of something occurs later in sequence or development than another.
-
B.
originalForm
Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
-
C.
predecessorStateForm
chosen
Indicates that one state form directly precedes another in a temporal or historical sequence.
-
D.
currentForm
Indicates the present or most recently adopted version, shape, or state that something currently has.
-
E.
previousHome
Indicates that one entity served as a former or prior residence or home of another entity.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.