Triple
T11721401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telephone Communication Limited |
E278639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical name expansion |
C1289
|
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 name expansion Context triple: [Telephone Communication Limited, instanceOf, historical name expansion]
-
A.
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.
-
B.
former name
chosen
A former name is a previous designation or title by which an entity, such as a person, organization, or place, was once known before being officially changed.
-
C.
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.
-
D.
geographical names authority
A geographical names authority is an entity or system responsible for standardizing, maintaining, and providing authoritative information on the official names and spellings of geographic places.
-
E.
traditional name
A traditional name is a personal name passed down through generations within a culture, family, or community, reflecting historical, religious, or cultural heritage.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.