Triple
T3794478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland national under-21 football team |
E89734
|
entity |
| Predicate | representsAgeGroup |
P13483
|
FINISHED |
| Object | players under 21 years old |
—
|
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: players under 21 years old | Statement: [Poland national under-21 football team, representsAgeGroup, players under 21 years old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsAgeGroup Context triple: [Poland national under-21 football team, representsAgeGroup, players under 21 years old]
-
A.
portraysAgeGroup
chosen
Indicates that one entity depicts or represents another entity as belonging to a particular age group.
-
B.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
C.
ageGroupRole
Indicates the role or function an entity has within a specific age group classification.
-
D.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.