Triple
T33539821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Don Award |
E859039
|
entity |
| Predicate | hasTeamRestriction |
P55023
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [The Don Award, hasTeamRestriction, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamRestriction Context triple: [The Don Award, hasTeamRestriction, no]
-
A.
hasTierRestriction
Indicates that an entity is limited or governed by specific access or service tiers, restricting what applies at each tier.
-
B.
squadRestrictionForInvitedTeams
Indicates a constraint or rule that applies to the squad composition or size specifically for teams that have been invited.
-
C.
leagueRestriction
Indicates a constraint or rule that limits participation, eligibility, or activity within a particular league.
-
D.
hasAwardRestriction
chosen
Indicates that there is a limitation, condition, or constraint placed on receiving or granting an award.
-
E.
hasCoverageRestriction
Indicates that there is a limitation, exclusion, or condition applied to the scope or extent of coverage provided.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 1:39 a.m.