Triple
T20230189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Sox Park |
E495493
|
entity |
| Predicate | teamTypeOfTenant |
P18037
|
FINISHED |
| Object | professional baseball team |
—
|
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: professional baseball team | Statement: [Red Sox Park, teamTypeOfTenant, professional baseball team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamTypeOfTenant Context triple: [Red Sox Park, teamTypeOfTenant, professional baseball team]
-
A.
tenantType
chosen
Indicates the classification or category of a tenant in a tenancy or rental relationship.
-
B.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
C.
leagueLevelOfTenant
Indicates the competitive league tier or division in which the tenant entity participates or is classified.
-
D.
parentCompanyOfTenants
Indicates that one company serves as the parent or owning company of one or more tenant entities.
-
E.
alsoTenant
Indicates that two or more entities share the status of being tenants, typically occupying the same property or rental arrangement.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fdce9d081909752a6a1e15283ba |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.