Triple
T22272352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAU Volleyball |
E550508
|
entity |
| Predicate | ageDivisionStructure |
P56466
|
FINISHED |
| Object | age-based divisions |
—
|
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: age-based divisions | Statement: [AAU Volleyball, ageDivisionStructure, age-based divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageDivisionStructure Context triple: [AAU Volleyball, ageDivisionStructure, age-based divisions]
-
A.
ageGroupStructure
chosen
Indicates how a population or set of entities is distributed across different age groups or age categories.
-
B.
divisionOrStructure
Indicates a relationship where one entity is an internal division, department, or structural subunit that is organizationally contained within another entity.
-
C.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
D.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
E.
formsDivisionWith
Indicates that one entity combines with another to create or constitute a division or subgroup within a larger organization or structure.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea449648190bb89ca292d32f59d |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.