Triple
T13487891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muda Gate |
E318552
|
entity |
| Predicate | roleInUrbanFabric |
P8652
|
FINISHED |
| Object | marks entrance to the old town |
—
|
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: marks entrance to the old town | Statement: [Muda Gate, roleInUrbanFabric, marks entrance to the old town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUrbanFabric Context triple: [Muda Gate, roleInUrbanFabric, marks entrance to the old town]
-
A.
roleInUrbanPlan
Indicates the specific function, responsibility, or position an entity holds within an urban planning context or scheme.
-
B.
urbanDesigner
Indicates a relationship where an entity practices or is responsible for planning and designing urban spaces, environments, or city layouts.
-
C.
hasUrbanPlanner
Indicates that an entity is associated with or utilizes a specific urban planner responsible for planning or managing its urban development.
-
D.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
-
E.
hasUrbanRole
Indicates that an entity plays a specific functional or social role within an urban or city context.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.