Triple
T34749054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lechia |
E1001717
|
entity |
| Predicate | countryNameType |
P203397
|
FINISHED |
| Object | exonym/endonym variant |
—
|
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: exonym/endonym variant | Statement: [Lechia, countryNameType, exonym/endonym variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryNameType Context triple: [Lechia, countryNameType, exonym/endonym variant]
-
A.
countryNameInISO
Indicates that the country’s name is expressed using the ISO-standardized country naming or coding format.
-
B.
countryDeJure
Indicates that one entity is the legally recognized (de jure) country having sovereignty or authority over another entity.
-
C.
countryOrTerritory
Indicates that one entity is a country or territory associated with, or characterized by, another entity.
-
D.
countryType
Indicates the classification or category of a country based on a specified typology (e.g., political, economic, or geographic type).
-
E.
commonNameCountry
Indicates that a given name is the commonly used or widely recognized name for a particular country.
- F. None of above. chosen
Provenance (4 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
| PDg | Predicate description generation | batch_6a0174e7e4c88190b8d81c3d78294f94 |
completed | May 11, 2026, 6:19 a.m. |
Created at: May 3, 2026, 3:59 p.m.