Triple
T13798722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storhamar Håndball |
E331581
|
entity |
| Predicate | usesNumberOfPlayersOnCourt |
P89523
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Storhamar Håndball, usesNumberOfPlayersOnCourt, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNumberOfPlayersOnCourt Context triple: [Storhamar Håndball, usesNumberOfPlayersOnCourt, 7]
-
A.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
B.
typicalNumberOfPlayers
Indicates the usual or standard number of players involved in participating in an activity or game.
-
C.
numberOfPlayersPerTeam
chosen
Indicates the quantity of players that are assigned to or allowed on each team in a given context.
-
D.
playerNumber
Indicates the specific jersey or identification number assigned to a player within a team or game context.
-
E.
hasCourtSurface
Indicates that something (such as a court or playing area) possesses a specific type of surface.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ce9148190b23370f6a522ff7a |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.