Triple
T470229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL Premier Development League |
E8538
|
entity |
| Predicate | typicalPlayerAgeRange |
P2736
|
FINISHED |
| Object | 18–23 |
—
|
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: 18–23 | Statement: [USL Premier Development League, typicalPlayerAgeRange, 18–23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayerAgeRange Context triple: [USL Premier Development League, typicalPlayerAgeRange, 18–23]
-
A.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
-
C.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
D.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
E.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.