Triple
T38548803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schemnitz |
E925047
|
entity |
| Predicate | referentCountry |
P71182
|
FINISHED |
| Object | Slovakia |
—
|
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: Slovakia | Statement: [Schemnitz, referentCountry, Slovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referentCountry Context triple: [Schemnitz, referentCountry, Slovakia]
-
A.
countryOfReferent
chosen
Indicates that one entity is the country with which the referenced entity (the referent) is associated or to which it belongs.
-
B.
primaryReferenceCountry
Indicates the main country that serves as the primary point of reference or association for the related entity.
-
C.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
-
D.
associatedCountryAtTheTime
Indicates the country with which an entity was linked or affiliated during a specific historical time or event, rather than its current or permanent country association.
-
E.
nativeCountry
Indicates the country in which an entity (typically a person) was born or is originally from.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.