Triple
T560454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl District |
E13437
|
entity |
| Predicate | hasDemographicTrend |
P5318
|
FINISHED |
| Object | increasing 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: increasing property values | Statement: [Pearl District, hasDemographicTrend, increasing property values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemographicTrend Context triple: [Pearl District, hasDemographicTrend, increasing property values]
-
A.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
B.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
C.
demographics
Indicates the relationship of providing or characterizing statistical information about a population’s attributes, such as age, gender, income, or education.
-
D.
demographicImpact
Indicates how an action, event, or condition affects the size, structure, or composition of a population.
-
E.
demographicsNote
Indicates that there is an associated note or commentary describing demographic-related information about an entity.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499e13694819087a236bffa6601a9 |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.