Triple
T29123578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain national under-23 football team |
E738158
|
entity |
| Predicate | overagePlayersAllowedPerTournament |
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: [Spain national under-23 football team, overagePlayersAllowedPerTournament, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overagePlayersAllowedPerTournament Context triple: [Spain national under-23 football team, overagePlayersAllowedPerTournament, 3]
-
A.
allowsOveragePlayers
chosen
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
B.
capacityAfterTournament
Indicates the resulting capacity of something after a tournament has taken place or been completed.
-
C.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
D.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
E.
postTournamentCapacity
Indicates the capacity or size of something after a tournament has concluded.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:26 a.m.