Triple
T22288009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA 3x3 U18 World Cup |
E550914
|
entity |
| Predicate | numberOfSubstitutesPerTeam |
P67575
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [FIBA 3x3 U18 World Cup, numberOfSubstitutesPerTeam, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSubstitutesPerTeam Context triple: [FIBA 3x3 U18 World Cup, numberOfSubstitutesPerTeam, 1]
-
A.
substitutesPerTeam
chosen
Indicates the number of substitute players allowed or used by each team in a given context.
-
B.
originalPlayersPerTeam
Indicates the number of players that each team initially had at the start of a game or season.
-
C.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
D.
numberOfPlayersPerTeam
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
E.
replacementPlayersUsed
Indicates that substitute or backup players were brought in to take the place of original players in a game or event.
- 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_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.