Triple
T27545517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korea under-23 national football team |
E695348
|
entity |
| Predicate | overAgePlayersAllowed |
P23145
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [South Korea under-23 national football team, overAgePlayersAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overAgePlayersAllowed Context triple: [South Korea under-23 national football team, overAgePlayersAllowed, yes]
-
A.
allowsOveragePlayers
chosen
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
B.
typicalAgeRangeOfPlayers
Indicates the usual age range of people who typically play or participate in something.
-
C.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
D.
professionalPlayersAllowedFrom
Indicates that professional players are permitted to participate starting from a specified point, such as a date, level, or stage.
-
E.
featuredPlayerAge
Indicates the age of the player who is designated as the featured or highlighted participant in a given context.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f840a588190919f31170d31b0c9 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:32 p.m.