Triple
T24011222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan de la Frontera de Huamanga |
E594534
|
entity |
| Predicate | hasHistoricalNameType |
P47064
|
FINISHED |
| Object | colonial Spanish toponym |
—
|
LITERAL FINISHED |
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: colonial Spanish toponym | Statement: [San Juan de la Frontera de Huamanga, hasHistoricalNameType, colonial Spanish toponym]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalNameType Context triple: [San Juan de la Frontera de Huamanga, hasHistoricalNameType, colonial Spanish toponym]
-
A.
hasHistoricNameVariant
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
B.
historicalNameType
chosen
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
C.
hasHistoricalNameChangeReason
Indicates that there is a specific reason or cause associated with a change in an entity’s historical name.
-
D.
hasHistoricNickname
Indicates that an entity is known by a nickname that has historical significance or longstanding traditional use.
-
E.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d59d6a2c8190860a44c056030826 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:41 p.m.