Triple
T5867563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany under-21 national football team |
E130432
|
entity |
| Predicate | playerSelection |
P31058
|
FINISHED |
| Object | German-eligible youth 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: German-eligible youth players | Statement: [Germany under-21 national football team, playerSelection, German-eligible youth players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerSelection Context triple: [Germany under-21 national football team, playerSelection, German-eligible youth players]
-
A.
teamSelection
chosen
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
B.
regulatesPlayerSelection
Indicates that an entity sets or enforces rules or constraints governing how players are chosen or selected.
-
C.
AllWNBATeamSelection
Indicates that a player has been selected to an All-WNBA Team for a given season or time period.
-
D.
playerNumber
Indicates the specific jersey or identification number assigned to a player within a team or game context.
-
E.
decidingOpponent
Indicates that one entity is the opponent or counterpart responsible for making a decision that affects another entity.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.