Triple
T14740950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andingmen Gate site |
E346342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former city gate location |
C28135
|
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: former city gate location Context triple: [Andingmen Gate site, instanceOf, former city gate location]
-
A.
former city gate site
chosen
A former city gate site is a location where a historic gateway that once controlled access through a city’s defensive walls previously stood, even if the physical structure no longer exists.
-
B.
ancient city gate
An ancient city gate is a monumental architectural structure that controlled access to a fortified settlement, often serving defensive, ceremonial, and administrative functions.
-
C.
medieval city gate
A medieval city gate is a fortified architectural structure that controls access to a walled town or city, combining defensive features like towers and portcullises with symbolic and administrative functions.
-
D.
former castle site
A former castle site is a location where a castle once stood but has since been demolished, ruined, or otherwise lost its original structure, though traces or historical evidence of the castle remain.
-
E.
former town hall
A former town hall is a building that once served as the central administrative and civic meeting place for a municipality but has since been repurposed or no longer functions in that official capacity.
- F. None of above.
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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:30 a.m.