Triple
T25618465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bendigo Pioneers |
E642225
|
entity |
| Predicate | focusAgeGroup |
P19123
|
FINISHED |
| Object | under-18 players |
—
|
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: under-18 players | Statement: [Bendigo Pioneers, focusAgeGroup, under-18 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusAgeGroup Context triple: [Bendigo Pioneers, focusAgeGroup, under-18 players]
-
A.
ageGroup
chosen
Indicates the categorical age range or bracket to which an entity belongs.
-
B.
ageGroupInvolved
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
-
C.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
-
D.
ageGroupIndicated
Indicates that a specific age range or category is identified or assigned to an entity.
-
E.
ageType
Indicates the specific categorization or classification of an age value (e.g., actual, estimated, range-based) associated with an 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 5:02 p.m.