Triple
T1263163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL Trophy |
E12543
|
entity |
| Predicate | squadRestrictionForInvitedTeams |
P24879
|
FINISHED |
| Object | primarily under-21 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: primarily under-21 players | Statement: [EFL Trophy, squadRestrictionForInvitedTeams, primarily under-21 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: squadRestrictionForInvitedTeams Context triple: [EFL Trophy, squadRestrictionForInvitedTeams, primarily under-21 players]
-
A.
teamEligibility
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
B.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
C.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
-
D.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
-
E.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc8d6908190a5b2cf1051cc6d5e |
completed | March 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc218cb8819090bff71ac7107a03 |
completed | March 1, 2026, 10:22 p.m. |
Created at: March 1, 2026, 7:50 p.m.