Triple
T27994554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Indoor Football Association |
E706974
|
entity |
| Predicate | numberOfPlayersOnFieldPerTeam |
P39852
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [American Indoor Football Association, numberOfPlayersOnFieldPerTeam, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPlayersOnFieldPerTeam Context triple: [American Indoor Football Association, numberOfPlayersOnFieldPerTeam, 8]
-
A.
numberOfTeamsOnFieldPerSide
Indicates how many teams are present on the field for each opposing side during play.
-
B.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
C.
playersPerSideOnField
chosen
Indicates the number of players from each team that are simultaneously present on the field during play.
-
D.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
E.
hasNumberOfTeamsOnFieldPerSide
Indicates the number of teams that are simultaneously present on the field on each opposing side in a game or sport.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: April 27, 2026, 7:52 p.m.