Triple
T32477358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruguayan national football teams |
E830011
|
entity |
| Predicate | ageLevels |
P71516
|
FINISHED |
| Object | senior |
—
|
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 | Statement: [Uruguayan national football teams, ageLevels, senior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageLevels Context triple: [Uruguayan national football teams, ageLevels, senior]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
C.
ageType
Indicates the specific categorization or classification of an age value (e.g., actual, estimated, range-based) associated with an entity.
-
D.
ageVariants
Indicates that one entity is an alternative form or version of another distinguished specifically by age (e.g., younger/older or different life-stage variants).
-
E.
representedAgeLevel
chosen
Indicates that one entity corresponds to, or is categorized under, a particular age level or age group.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3925f5c8190b2cd06374266f5ba |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:58 a.m.