Triple
T13269270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seals Stadium |
E316011
|
entity |
| Predicate | tenantsEndDate |
P20545
|
FINISHED |
| Object | San Francisco Seals 1957 |
—
|
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: San Francisco Seals 1957 | Statement: [Seals Stadium, tenantsEndDate, San Francisco Seals 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantsEndDate Context triple: [Seals Stadium, tenantsEndDate, San Francisco Seals 1957]
-
A.
tenantsEnd
chosen
Indicates that a tenancy or lease relationship between parties comes to an end at a specified time or under certain conditions.
-
B.
primaryTenantUntil
Indicates that an entity serves as the main or principal tenant of a property or lease up to a specified end date.
-
C.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
D.
tenantsStart
Indicates that a tenancy relationship begins or is initiated at a specific time or event.
-
E.
leaseExtendedUntil
Indicates that an existing lease agreement has been prolonged so that its validity now continues up to a specified end date.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.