Triple
T22288066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 rules |
E550915
|
entity |
| Predicate | fouls7To9 |
P67606
|
FINISHED |
| Object | team fouls 7–9 result in 2 free throws |
—
|
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: team fouls 7–9 result in 2 free throws | Statement: [FIBA 3x3 rules, fouls7To9, team fouls 7–9 result in 2 free throws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fouls7To9 Context triple: [FIBA 3x3 rules, fouls7To9, team fouls 7–9 result in 2 free throws]
-
A.
penaltyFrom7thFoul
chosen
Indicates that a penalty situation arises as a result of committing a seventh foul.
-
B.
foulLimitPerPlayer
Indicates the maximum number of fouls that any single player is allowed to commit before a penalty or disqualification occurs.
-
C.
foulLimitPerTeam
Indicates the maximum number of fouls that a single team is allowed to commit within a defined game or competition context.
-
D.
penaltyFrom10thFoul
Indicates that a penalty situation arises as a result of a team or player committing their tenth foul.
-
E.
hasFoulType
Indicates that an entity is associated with or characterized by a specific type or category of foul (e.g., in a game, sport, or rule system).
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560896348190985725ac8ad406b3 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.