Triple
T14861986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL clubs |
E349516
|
entity |
| Predicate | salaryRegulation |
P115928
|
FINISHED |
| Object | AFL salary cap |
—
|
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: AFL salary cap | Statement: [AFL clubs, salaryRegulation, AFL salary cap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salaryRegulation Context triple: [AFL clubs, salaryRegulation, AFL salary cap]
-
A.
salary
Indicates the amount of monetary compensation an entity receives, typically on a regular basis, for work or services performed.
-
B.
salaryType
Indicates the classification or structure of compensation associated with an entity, such as whether pay is salaried, hourly, commission-based, or another type.
-
C.
salaryProtection
Indicates that an arrangement exists to maintain or safeguard an individual's salary level against reduction under certain conditions.
-
D.
basisOfWageDetermination
Indicates the factor or criteria used to determine the amount or structure of a wage.
-
E.
payScale
Indicates the compensation level or salary range assigned to an entity, typically reflecting its relative pay or grade within a structured system.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.