Triple
T5022010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Dallas |
E112874
|
entity |
| Predicate | historicalClass |
P9609
|
FINISHED |
| Object | working-class neighborhood |
—
|
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: working-class neighborhood | Statement: [West Dallas, historicalClass, working-class neighborhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalClass Context triple: [West Dallas, historicalClass, working-class neighborhood]
-
A.
historicalCategory
chosen
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
B.
historicalClassificationEnd
Indicates the point in time when a particular historical classification or categorization of an entity ceases to be valid.
-
C.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73656edc8190b802ad38d9552b58 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.