Triple
T2738172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Water |
E60681
|
entity |
| Predicate | hasPropertyMarket |
P16332
|
FINISHED |
| Object | high-value housing |
—
|
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: high-value housing | Statement: [Virginia Water, hasPropertyMarket, high-value housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyMarket Context triple: [Virginia Water, hasPropertyMarket, high-value housing]
-
A.
propertyMarket
chosen
Indicates a relationship where real estate or properties are being offered, traded, or evaluated within a market context.
-
B.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
C.
propertyStatus
Indicates the current condition, state, or classification assigned to a property within a given context (e.g., availability, legal standing, or operational state).
-
D.
homeMarket
Indicates the primary geographic or economic market in which an entity is based or predominantly operates.
-
E.
hasHouses
Indicates that one entity possesses, controls, or contains one or more houses in relation to another entity or context.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb147a588190829b74fe05b3a114 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.