Triple
T37033170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grange |
E916550
|
entity |
| Predicate | realEstateValue |
P139294
|
FINISHED |
| Object | high property prices |
—
|
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 prices | Statement: [Grange, realEstateValue, high property prices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realEstateValue Context triple: [Grange, realEstateValue, high property prices]
-
A.
estateValue
Indicates the monetary worth or assessed value of an estate in the context of ownership, inheritance, or property holdings.
-
B.
houseValues
chosen
Indicates a relationship where specific houses are associated with their corresponding numerical values, such as prices or appraised worth.
-
C.
realEstate
Indicates a relationship where an entity owns, manages, or is otherwise associated with real property such as land or buildings.
-
D.
realEstateProject
Indicates a relationship where an entity is involved in, associated with, or represents a specific real estate development project.
-
E.
medianHomeValues
Indicates the typical (middle) home price or value within a given area or group of properties.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.