Triple
T5528609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League under-21 team |
E144988
|
entity |
| Predicate | canUsePlayersFrom |
P51793
|
FINISHED |
| Object | club academy |
—
|
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: club academy | Statement: [Premier League under-21 team, canUsePlayersFrom, club academy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUsePlayersFrom Context triple: [Premier League under-21 team, canUsePlayersFrom, club academy]
-
A.
allowsForeignPlayers
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
-
B.
managedPlayers
Indicates that one entity has managerial responsibility or authority over the players represented by the other entity.
-
C.
intendedPlayers
Indicates the players for whom something (such as a game, item, or activity) is designed or meant to be used.
-
D.
regulatesPlayerSelection
chosen
Indicates that an entity sets or enforces rules or constraints governing how players are chosen or selected.
-
E.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8b6c348190b7d414dc1907d09a |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.