Triple
T980604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Mariners |
E21157
|
entity |
| Predicate | wildCardBerths |
P13621
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Seattle Mariners, wildCardBerths, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildCardBerths Context triple: [Seattle Mariners, wildCardBerths, 1995]
-
A.
wildCardBerthsCount
Indicates the number of wildcard berths (extra or non-standard qualification spots) allocated in a competition or selection process.
-
B.
wildCardBerth
chosen
Indicates that an entity receives a berth or qualification through a wildcard allocation rather than through standard qualification criteria.
-
C.
hasReservedSeats
Indicates that specific seats have been set aside or allocated in advance for a particular entity or purpose.
-
D.
hasBusBays
Indicates that a location or facility is equipped with one or more designated bus bays for buses to stop, load, or unload passengers.
-
E.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47b58ec81908d95f151b9af3dae |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:40 p.m.