Triple
T16820726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concord Mills |
E408881
|
entity |
| Predicate | hasTenantMix |
P60731
|
FINISHED |
| Object | national brand outlets |
—
|
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: national brand outlets | Statement: [Concord Mills, hasTenantMix, national brand outlets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTenantMix Context triple: [Concord Mills, hasTenantMix, national brand outlets]
-
A.
hasTenants
Indicates that an entity occupies or rents space from another entity as its tenant.
-
B.
hasMajorTenantType
chosen
Indicates that an entity (such as a property or building) is associated with a primary or predominant type of tenant.
-
C.
hasTenantSince
Indicates that an entity has been the tenant of another entity starting from a specified point in time.
-
D.
intendedTenant
Indicates that one entity is designated or expected to occupy or lease another entity (such as a property) as a tenant.
-
E.
supportsMultiTenancy
Indicates that the subject system or component is capable of serving and isolating multiple distinct tenants or customer environments within a single deployment.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e6b59c8190ad562a80e71ce54c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.