Triple
T38294023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanškroun, Czechoslovakia |
E1022440
|
entity |
| Predicate | hasHistoricalCountryName |
P175129
|
FINISHED |
| Object | Czechoslovakia |
—
|
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: Czechoslovakia | Statement: [Lanškroun, Czechoslovakia, hasHistoricalCountryName, Czechoslovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalCountryName Context triple: [Lanškroun, Czechoslovakia, hasHistoricalCountryName, Czechoslovakia]
-
A.
previousNameOfCountry
Indicates that one country name was formerly used as the official name of another country.
-
B.
isHistoricalName
chosen
Indicates that a given name is a former or past designation historically used for an entity.
-
C.
hasHistoricalCountrySubdivision
Indicates that one entity was a territorial or administrative subdivision of a historical country.
-
D.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
E.
existedBeforeCountryNameChange
Indicates that an entity existed prior to the point in time when a country changed its official name.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:30 p.m.