Triple
T35998032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 Asia Cup |
E1041046
|
entity |
| Predicate | teamFoulLimit |
P67605
|
FINISHED |
| Object | 6 team fouls before penalty |
—
|
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: 6 team fouls before penalty | Statement: [FIBA 3x3 Asia Cup, teamFoulLimit, 6 team fouls before penalty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamFoulLimit Context triple: [FIBA 3x3 Asia Cup, teamFoulLimit, 6 team fouls before penalty]
-
A.
foulLimitPerTeam
chosen
Indicates the maximum number of fouls that a single team is allowed to commit within a defined game or competition context.
-
B.
foulLimitPerPlayer
Indicates the maximum number of fouls that any single player is allowed to commit before a penalty or disqualification occurs.
-
C.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
D.
foulsPenalizedBy
Indicates that a foul committed by one party is punished or sanctioned by another authority or rule-enforcing entity.
-
E.
fouls6AndBelow
Indicates that one entity commits a foul or infraction against another, where the total number of such fouls is six or fewer.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.