Triple
T37638226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sztumska Wieś |
E936545
|
entity |
| Predicate | countryDuring1635 |
P81295
|
FINISHED |
| Object | Polish–Lithuanian Commonwealth |
E24175
|
NE 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: Polish–Lithuanian Commonwealth | Statement: [Sztumska Wieś, countryDuring1635, Polish–Lithuanian Commonwealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryDuring1635 Context triple: [Sztumska Wieś, countryDuring1635, Polish–Lithuanian Commonwealth]
-
A.
countryDuring16thCentury
Indicates that an entity functioned as a country or sovereign political unit during the 16th century.
-
B.
countryDuring17thCentury
chosen
Indicates that an entity functioned as a country during some or all of the 17th century.
-
C.
countryDuring18thCentury
Indicates that an entity functioned as a country or sovereign political unit at some time during the 18th century.
-
D.
countryDuringRussianEmpirePeriod
Indicates that a given country existed or is considered in the context of the historical period of the Russian Empire.
-
E.
countryDuringTsardom
Indicates that an entity functioned as a country or political unit during the historical period of tsardom.
- F. None of above.
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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4167f11ca481908c659e0878583e65 |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.