Triple
T7124708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mech (historical name) |
E166030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical language name |
C3354
|
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: historical language name Context triple: [Mech (historical name), instanceOf, historical language name]
-
A.
historical language
chosen
A historical language is a natural language studied in the context of its past stages, evolution, and usage within specific historical periods and societies.
-
B.
historical language stage
A historical language stage is a distinct, temporally bounded phase in the development of a language, characterized by relatively stable structural features and documented through historical evidence.
-
C.
historical place name
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
D.
historical ethnonym
A historical ethnonym is a name or label historically used to designate a particular ethnic group, people, or population, often reflecting past cultural, political, or linguistic contexts that may differ from present-day usage.
-
E.
ancient language
An ancient language is a historically significant, no-longer-natively-spoken linguistic system preserved through inscriptions, manuscripts, and scholarly reconstruction.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:44 p.m.