Triple
T6837917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Stadium |
E157495
|
entity |
| Predicate | tenantTo |
P65700
|
FINISHED |
| Object | Texas Rangers 1993 |
—
|
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: Texas Rangers 1993 | Statement: [Arlington Stadium, tenantTo, Texas Rangers 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantTo Context triple: [Arlington Stadium, tenantTo, Texas Rangers 1993]
-
A.
alsoTenantTo
Indicates that one entity is also a tenant of the same property or landlord as another entity, in addition to any other existing relationships.
-
B.
alsoTenantFrom
Indicates that one entity is also a tenant originating from the same source, context, or provider as another entity.
-
C.
tenantBecame
Indicates that an entity transitioned into the role or status of a tenant at a particular time or under specific conditions.
-
D.
tenantsFrom
Indicates that one or more tenants originate from, are associated with, or are derived from a specified source entity.
-
E.
tenantedBy
chosen
Indicates that a property, land, or space is occupied or leased by a specific tenant.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67db4008190b86b497bf6f0c73a |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.