Triple
T3401606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbes Field |
E71665
|
entity |
| Predicate | tenantStart |
P20544
|
FINISHED |
| Object | Pittsburgh Pirates 1909 |
—
|
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: Pittsburgh Pirates 1909 | Statement: [Forbes Field, tenantStart, Pittsburgh Pirates 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantStart Context triple: [Forbes Field, tenantStart, Pittsburgh Pirates 1909]
-
A.
tenantsStart
chosen
Indicates that a tenancy relationship begins or is initiated at a specific time or event.
-
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.
inauguralSeasonTenant
Indicates that the subject entity served as a tenant (e.g., occupant or user of a venue or facility) during the venue’s inaugural season.
-
D.
tenantType
Indicates the classification or category of a tenant in a tenancy or rental relationship.
-
E.
tenantBecame
Indicates that an entity transitioned into the role or status of a tenant at a particular time or under specific conditions.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c96d7c8190a1f9d035996f79e3 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.