Triple
T22556158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de las Ocho Calles |
E557687
|
entity |
| Predicate | streetPlanType |
P47409
|
FINISHED |
| Object | radial layout |
—
|
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: radial layout | Statement: [Plaza de las Ocho Calles, streetPlanType, radial layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetPlanType Context triple: [Plaza de las Ocho Calles, streetPlanType, radial layout]
-
A.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
B.
hasStreetPlan
chosen
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
C.
floorPlanType
Indicates the specific layout or configuration category that a floor plan belongs to (e.g., studio, 1-bedroom, open-plan).
-
D.
streetOrAreaType
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
E.
urbanPlanBy
Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7a4a3c81908fc87f48b6dcbbf7 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.