Triple
T1087394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baker Bowl |
E24082
|
entity |
| Predicate | mainTenantPeriod |
P7934
|
FINISHED |
| Object | Philadelphia Phillies 1887–1938 |
—
|
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: Philadelphia Phillies 1887–1938 | Statement: [Baker Bowl, mainTenantPeriod, Philadelphia Phillies 1887–1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTenantPeriod Context triple: [Baker Bowl, mainTenantPeriod, Philadelphia Phillies 1887–1938]
-
A.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
B.
locationPeriod
chosen
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
tenantType
Indicates the classification or category of a tenant in a tenancy or rental relationship.
-
D.
anchorTenant
Indicates that an entity serves as a primary or major tenant whose presence helps attract other tenants or users to a shared space or platform.
-
E.
tenantsStart
Indicates that a tenancy relationship begins or is initiated at a specific time or event.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.