Triple
T15473347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Ten wrestling |
E376718
|
entity |
| Predicate | hasPrimaryAgeGroup |
P29430
|
FINISHED |
| Object | college-aged athletes |
—
|
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: college-aged athletes | Statement: [Big Ten wrestling, hasPrimaryAgeGroup, college-aged athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAgeGroup Context triple: [Big Ten wrestling, hasPrimaryAgeGroup, college-aged athletes]
-
A.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
B.
hasLowerAge
Indicates that one entity is younger in age than another entity.
-
C.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
D.
hasAgeFocus
chosen
Indicates a relationship where something is characterized or distinguished by a particular age group or age-related emphasis.
-
E.
hasJuniorAgeCategory
Indicates that an entity is associated with, or classified under, a junior age category within a given context or system.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.