Triple
T16382652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USA Outdoor Track and Field Championships |
E397845
|
entity |
| Predicate | governsAgeCategory |
P110301
|
FINISHED |
| Object | senior/open |
—
|
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: senior/open | Statement: [USA Outdoor Track and Field Championships, governsAgeCategory, senior/open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsAgeCategory Context triple: [USA Outdoor Track and Field Championships, governsAgeCategory, senior/open]
-
A.
hasAgeClassification
chosen
Indicates that an entity is associated with a specific age-based category or grouping.
-
B.
foundedAsAgeCategory
Indicates that an organization, group, or entity was originally established specifically to serve or represent a particular age category.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319ddcef08190a2081855b5cf6762 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.