Triple
T37196030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perth Wildcats |
E921594
|
entity |
| Predicate | finalsAppearancesConsecutive |
P198980
|
FINISHED |
| Object | 34 |
—
|
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: 34 | Statement: [Perth Wildcats, finalsAppearancesConsecutive, 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalsAppearancesConsecutive Context triple: [Perth Wildcats, finalsAppearancesConsecutive, 34]
-
A.
runnerUpConsecutiveAppearances
Indicates that an entity has achieved runner-up status in a competition for a specified number of consecutive appearances or editions.
-
B.
consecutiveGamesPlayed
Indicates that an entity has participated in a series of games without interruption, one immediately following another.
-
C.
runnerUpFinalsAppearances
Indicates the number of times an entity has appeared in a final and finished as the runner-up.
-
D.
finalFourAppearancesWith
Indicates that the entities have appeared together in the NCAA basketball Final Four in the same tournament.
-
E.
consecutiveWinningSeasons
Indicates that an entity (such as a team or individual) has achieved winning seasons in back-to-back or uninterrupted consecutive years.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
| PDg | Predicate description generation | batch_69ff17bda59c8190b27c524f3e01c6df |
completed | May 9, 2026, 11:17 a.m. |
Created at: May 3, 2026, 4:15 p.m.