Triple
T15765999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union II |
E382219
|
entity |
| Predicate | playerAgeFocus |
P29430
|
FINISHED |
| Object | young professional 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: young professional players | Statement: [Union II, playerAgeFocus, young professional players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerAgeFocus Context triple: [Union II, playerAgeFocus, young professional players]
-
A.
hasAgeFocus
chosen
Indicates a relationship where something is characterized or distinguished by a particular age group or age-related emphasis.
-
B.
featuredPlayerAge
Indicates the age of the player who is designated as the featured or highlighted participant in a given context.
-
C.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
D.
youthAcademyFocus
Indicates that an organization or program is primarily dedicated to developing and training young or junior participants.
-
E.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b8154881908afe5191e6424f15 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.