Triple
T17582999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USISL Premier League |
E428249
|
entity |
| Predicate | ageProfileOfPlayers |
P13613
|
FINISHED |
| Object | college-age players |
—
|
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-age players | Statement: [USISL Premier League, ageProfileOfPlayers, college-age players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageProfileOfPlayers Context triple: [USISL Premier League, ageProfileOfPlayers, college-age players]
-
A.
featuredPlayerAge
Indicates the age of the player who is designated as the featured or highlighted participant in a given context.
-
B.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
C.
typicalPlayerProfile
chosen
Indicates the usual or characteristic attributes, behaviors, or demographics associated with a representative player in a given context.
-
D.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
typicalAgeOfWinner
Indicates the age that is most commonly observed for entities that win a particular competition, award, or event.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463cf556881908d2935b3761f65df |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.