Triple
T14861979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL clubs |
E349516
|
entity |
| Predicate | talentPathway |
P13378
|
FINISHED |
| Object | junior football systems |
—
|
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: junior football systems | Statement: [AFL clubs, talentPathway, junior football systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talentPathway Context triple: [AFL clubs, talentPathway, junior football systems]
-
A.
careerPath
Indicates the progression or sequence of roles, positions, or occupations that an individual follows over time in their professional life.
-
B.
talentPipelineRole
Indicates a role that an entity holds or plays within a talent acquisition or development pipeline.
-
C.
careerSystem
Indicates a relationship where an entity is part of, governed by, or operates within a particular career-related system or framework.
-
D.
developmentPathwayFor
chosen
Indicates that one entity serves as a route, mechanism, or process through which the development or progression of another entity occurs.
-
E.
nationalPathwayRole
Indicates the specific role or function an entity holds within a national-level pathway, framework, or process.
- 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_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. |
Created at: April 10, 2026, 1:54 a.m.