Triple
T11833591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slough Trading Estate |
E281457
|
entity |
| Predicate | hasNotableTenantType |
P60731
|
FINISHED |
| Object | multinational corporations |
—
|
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: multinational corporations | Statement: [Slough Trading Estate, hasNotableTenantType, multinational corporations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTenantType Context triple: [Slough Trading Estate, hasNotableTenantType, multinational corporations]
-
A.
hasMajorTenantType
chosen
Indicates that an entity (such as a property or building) is associated with a primary or predominant type of tenant.
-
B.
hasNotableClientType
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
-
C.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasTenants
Indicates that an entity occupies or rents space from another entity as its tenant.
-
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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62e7e408190998bebe346c82e89 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.