Triple
T27545518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korea under-23 national football team |
E695348
|
entity |
| Predicate | overAgePlayersLimit |
P23145
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [South Korea under-23 national football team, overAgePlayersLimit, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overAgePlayersLimit Context triple: [South Korea under-23 national football team, overAgePlayersLimit, 3]
-
A.
allowsOveragePlayers
chosen
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
B.
ageLimitException
Indicates that a specified age restriction does not apply or is waived under certain conditions.
-
C.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
D.
featuredPlayerAge
Indicates the age of the player who is designated as the featured or highlighted participant in a given context.
-
E.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
- 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_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:32 p.m.