Triple
T35782058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankara inscription |
E1034463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monumental inscription |
C27698
|
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: monumental inscription Context triple: [Ankara inscription, instanceOf, monumental inscription]
-
A.
commemorative inscription
chosen
A commemorative inscription is a formally written text, often engraved or carved on a durable surface, that records and honors a person, event, or achievement for posterity.
-
B.
hieroglyphic inscription monument
A hieroglyphic inscription monument is a physical structure, such as a stela, wall, or pillar, bearing carved or painted hieroglyphic texts that record religious, political, historical, or commemorative information.
-
C.
architectural inscription
An architectural inscription is a text or symbolic marking integrated into a building or structure that conveys information, commemoration, or meaning related to its purpose, creators, or historical context.
-
D.
religious inscription
A religious inscription is a text carved, written, or otherwise permanently recorded on a durable surface that conveys sacred messages, prayers, dedications, or doctrinal statements associated with a particular faith tradition.
-
E.
war memorial inscription
A war memorial inscription is a formally composed text engraved or displayed on a monument to commemorate individuals or groups who served or died in military conflict, often expressing remembrance, honor, and collective grief.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.