Triple
T10820862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missoula PaddleHeads |
E255364
|
entity |
| Predicate | beganPlayInPioneerLeague |
P26144
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Missoula PaddleHeads, beganPlayInPioneerLeague, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPlayInPioneerLeague Context triple: [Missoula PaddleHeads, beganPlayInPioneerLeague, 1999]
-
A.
beganInLeagueSeason
Indicates that an entity (such as a team, player, or competition) began its participation or activity during a specified league season.
-
B.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
C.
firstYearPlayed
chosen
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
-
D.
debutInLeague
Indicates the league in which an entity (typically a player or team) made its first official appearance.
-
E.
beganAmateurCareer
Indicates that an entity started its amateur-level career or involvement in a particular field or activity.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73449eee88190afa52c4e6ef96baa |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.