Triple
T6219882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadu |
E139082
|
entity |
| Predicate | hasCityLayoutType |
P48747
|
FINISHED |
| Object | grid plan |
—
|
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: grid plan | Statement: [Dadu, hasCityLayoutType, grid plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityLayoutType Context triple: [Dadu, hasCityLayoutType, grid plan]
-
A.
urbanLayout
chosen
Indicates how the spatial arrangement, organization, and structure of buildings, streets, and public spaces relate to one another within an urban area.
-
B.
hasColonialUrbanLayout
Indicates that an urban area’s spatial organization and street pattern follow a design imposed during a colonial period, reflecting colonial planning principles and control.
-
C.
hasStreetLayoutCenteredOn
Indicates that the spatial organization or pattern of streets in one place is arranged with a particular feature or location as its central focus or reference point.
-
D.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
-
E.
urbanDesignType
Indicates the specific category or style of urban design that characterizes or is applied to a place or project.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bbb768819099402d367f124639 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.