Triple
T9615108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake Bees |
E232198
|
entity |
| Predicate | hasLeagueMembershipStatus |
P18012
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [Salt Lake Bees, hasLeagueMembershipStatus, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueMembershipStatus Context triple: [Salt Lake Bees, hasLeagueMembershipStatus, active]
-
A.
membershipStatus
chosen
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
B.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
C.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
-
D.
membershipAsOf
Indicates that one entity is a member of another entity or group at a specific point in time or as of a given date.
-
E.
clubMembership
Indicates that an entity belongs to, is enrolled in, or holds membership status within a particular club.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9aabb6b88190b53547db885e0129 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.