Triple
T36989934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoDo neighborhood of Seattle |
E915065
|
entity |
| Predicate | sportsTeamTenant |
P22807
|
FINISHED |
| Object | Seattle Seahawks |
—
|
NE NERFINISHED |
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: Seattle Seahawks | Statement: [SoDo neighborhood of Seattle, sportsTeamTenant, Seattle Seahawks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsTeamTenant Context triple: [SoDo neighborhood of Seattle, sportsTeamTenant, Seattle Seahawks]
-
A.
sportsTeamTenancyStart
Indicates the date or point in time when an entity begins its occupancy or tenure as a sports team at a particular venue or location.
-
B.
majorTeamTenant
Indicates that a major sports team is the primary tenant or long-term occupant of a particular venue or facility.
-
C.
sportsTenant
chosen
Indicates that one entity occupies or uses a sports facility or venue as a tenant under some form of agreement or arrangement.
-
D.
sportsTeamPartialReturn
Indicates that a sports team has returned to competition or activity in a limited, incomplete, or transitional manner rather than fully resuming.
-
E.
sportsTeamOwned
Indicates that one entity is the owner (or part-owner) of a sports team 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.