Triple
T28639045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaffle |
E724868
|
entity |
| Predicate | usedByTeamSize |
P3668
|
FINISHED |
| Object | one per team at a time |
—
|
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: one per team at a time | Statement: [Quaffle, usedByTeamSize, one per team at a time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTeamSize Context triple: [Quaffle, usedByTeamSize, one per team at a time]
-
A.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
B.
teamSizeVariantOf
Indicates that one entity represents a variation of another entity specifically in terms of team size configuration or composition.
-
C.
typicalTeamSize
chosen
Indicates the usual or most common number of members that make up a given team.
-
D.
usedForTeam
Indicates that something is utilized or designated for use by a particular team.
-
E.
teamSizeFormat
Indicates how the size of a team is represented or formatted (e.g., as a number, range, or categorized label).
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 4:42 a.m.