Triple
T30264493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Outlet Mall |
E769598
|
entity |
| Predicate | notableTenantType |
P18037
|
FINISHED |
| Object | outlet stores |
—
|
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: outlet stores | Statement: [St. Louis Outlet Mall, notableTenantType, outlet stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTenantType Context triple: [St. Louis Outlet Mall, notableTenantType, outlet stores]
-
A.
notableTenant
Indicates that an entity is or has been a significant or noteworthy occupant or renter of a particular place or property.
-
B.
notableTenantAfterClosure
Indicates that an entity became a significant or noteworthy tenant of a property after that property had been closed or ceased its prior operations.
-
C.
tenantType
chosen
Indicates the classification or category of a tenant in a tenancy or rental relationship.
-
D.
notableServiceType
Indicates that the subject is associated with a particular type or category of service that is especially notable or significant.
-
E.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:42 p.m.