Triple
T11920941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finchampstead |
E283652
|
entity |
| Predicate | hasAffluence |
P44558
|
FINISHED |
| Object | affluent residential area |
—
|
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: affluent residential area | Statement: [Finchampstead, hasAffluence, affluent residential area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAffluence Context triple: [Finchampstead, hasAffluence, affluent residential area]
-
A.
isAffluentArea
chosen
Indicates that a given area is characterized by high wealth, income levels, or overall economic prosperity.
-
B.
isWealthy
Indicates that an entity possesses a high level of financial resources or assets relative to a given standard.
-
C.
locatedInAffluentArea
Indicates that something is situated within a geographically defined area characterized by high wealth, income, or socioeconomic status.
-
D.
hasRich
Indicates that an entity possesses or is characterized by a high level of wealth, abundance, or valuable resources.
-
E.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e1b08481909ed291667035f330 |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.