Triple
T28481823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Chelsea |
E720713
|
entity |
| Predicate | urbanIncorporation |
P167362
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Little Chelsea, urbanIncorporation, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanIncorporation Context triple: [Little Chelsea, urbanIncorporation, 19th century]
-
A.
incorporatedAsCity
Indicates that an entity was formally established and legally recognized as a city.
-
B.
formsUrbanAreaWith
Indicates that two or more settlements are geographically and functionally connected so that together they constitute a single continuous urban area.
-
C.
urbanAreaType
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
-
D.
provinceMetropolitanSee
Indicates that a metropolitan see (an archdiocesan seat) has ecclesiastical jurisdiction over, or is the principal see of, a given church province.
-
E.
isUrbanizedAround
Indicates that an area or region has developed urban characteristics or infrastructure surrounding a particular location or feature.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 2:56 a.m.