Triple
T22117490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Hill of Ambohimanga |
E546579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic fortified royal city |
C45823
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic fortified royal city Context triple: [Royal Hill of Ambohimanga, instanceOf, historic fortified royal city]
-
A.
historic city-state
A historic city-state is an independent, self-governing urban center and its surrounding territory that functioned as a sovereign political, economic, and cultural entity in a specific historical period.
-
B.
historic urban center
A historic urban center is a densely built core area of a city characterized by its preserved architectural heritage, traditional street patterns, and long-standing cultural, social, and economic significance.
-
C.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
D.
historic city quarter
A historic city quarter is an urban area characterized by preserved architecture, street patterns, and cultural landmarks that reflect the social, economic, and architectural history of a particular period.
-
E.
historic palace
A historic palace is a grand, architecturally significant residence once occupied by royalty or nobility, preserved as a cultural landmark that reflects the political, social, and artistic heritage of its era.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.