Triple
T26169875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirtha |
E654370
|
entity |
| Predicate | hasAlternativeHistoricalName |
P66486
|
FINISHED |
| Object | Cirta |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cirta | Statement: [Kirtha, hasAlternativeHistoricalName, Cirta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeHistoricalName Context triple: [Kirtha, hasAlternativeHistoricalName, Cirta]
-
A.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
B.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
C.
hasHistoricNameVariant
chosen
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
D.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
E.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
- F. None of above.
Provenance (3 batches)
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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 8:34 p.m.