Triple
T34687016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Generals |
E890779
|
entity |
| Predicate | hasGameOutcomePattern |
P179626
|
FINISHED |
| Object | rarely win against Harlem Globetrotters |
—
|
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: rarely win against Harlem Globetrotters | Statement: [Washington Generals, hasGameOutcomePattern, rarely win against Harlem Globetrotters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameOutcomePattern Context triple: [Washington Generals, hasGameOutcomePattern, rarely win against Harlem Globetrotters]
-
A.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
C.
hasGameEndCondition
Indicates that an entity specifies the condition or set of conditions under which a game is considered finished or concluded.
-
D.
playerOutcome
Indicates the result or consequence experienced by a player in a game, match, or scenario (such as winning, losing, or drawing).
-
E.
hasOutcomeClass
Indicates that something is associated with a particular category or type of outcome.
- F. None of above. chosen
Provenance (4 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234e20048190abe6a6ab8455754d |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.