Triple
T34983424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard de Walden Estate |
E1008876
|
entity |
| Predicate | primaryUseMix |
P206782
|
FINISHED |
| Object | residential |
—
|
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: residential | Statement: [Howard de Walden Estate, primaryUseMix, residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseMix Context triple: [Howard de Walden Estate, primaryUseMix, residential]
-
A.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
-
C.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
D.
mainlyUses
Indicates that one entity primarily relies on, employs, or utilizes another entity as its main tool, method, resource, or medium.
-
E.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
- F. None of above. chosen
Provenance (4 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.