Triple
T32549224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Light District of Amsterdam |
E831929
|
entity |
| Predicate | hasPolicyIssue |
P197856
|
FINISHED |
| Object | gentrification |
—
|
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: gentrification | Statement: [Red Light District of Amsterdam, hasPolicyIssue, gentrification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicyIssue Context triple: [Red Light District of Amsterdam, hasPolicyIssue, gentrification]
-
A.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
-
B.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
C.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
D.
hasSocialPolicy
Indicates that an entity possesses, adopts, or is governed by a particular social policy.
-
E.
hasPolicyInterestOf
Indicates that one entity holds or is associated with a specific policy interest belonging to or concerning another entity.
- F. None of above. chosen
Provenance (4 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: May 1, 2026, 1:02 a.m.