Triple
T25698149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pymble |
E644382
|
entity |
| Predicate | housingMarketCharacteristic |
P124397
|
FINISHED |
| Object | high property values |
—
|
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 property values | Statement: [Pymble, housingMarketCharacteristic, high property values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingMarketCharacteristic Context triple: [Pymble, housingMarketCharacteristic, high property values]
-
A.
realEstateMarketCharacteristic
chosen
Indicates a characteristic, condition, or defining feature of a real estate market.
-
B.
estateCharacteristic
Indicates that an estate possesses a particular attribute, quality, or defining feature.
-
C.
propertyMarket
Indicates a relationship where real estate or properties are being offered, traded, or evaluated within a market context.
-
D.
realEstateMarketSegment
Indicates the specific portion or category of the real estate market to which a property, transaction, or activity belongs (e.g., by price range, property type, or target buyer group).
-
E.
neighborhoodCharacteristic
Indicates that a particular characteristic, feature, or quality is associated with or describes a given neighborhood.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc60fb48190a45d46a8caef45bf |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 8:40 p.m.