Triple
T36197311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigeria Premier Football League clubs |
E1047163
|
entity |
| Predicate | playerLimitOnField |
P39852
|
FINISHED |
| Object | 11 players per team |
—
|
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: 11 players per team | Statement: [Nigeria Premier Football League clubs, playerLimitOnField, 11 players per team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerLimitOnField Context triple: [Nigeria Premier Football League clubs, playerLimitOnField, 11 players per team]
-
A.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
B.
playersPerSideOnField
chosen
Indicates the number of players from each team that are simultaneously present on the field during play.
-
C.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
D.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
E.
teamLimitType
Indicates the rule or constraint that defines how many members or teams are allowed within a given context.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:08 p.m.