Triple
T38235982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Designer Outlet Neumünster |
E1013620
|
entity |
| Predicate | typicalTenantCategory |
P18037
|
FINISHED |
| Object | fashion |
—
|
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: fashion | Statement: [Designer Outlet Neumünster, typicalTenantCategory, fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTenantCategory Context triple: [Designer Outlet Neumünster, typicalTenantCategory, fashion]
-
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.
originalTenantIndustry
Indicates the industry or business sector in which the original tenant operates or is classified.
-
D.
tenantsEndUse
Indicates that the specified end use or consumption activity is carried out by tenants rather than by the property owner or other parties.
-
E.
notableTenant
Indicates that an entity is or has been a significant or noteworthy occupant or renter of a particular place or property.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.