Triple
T3166038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazovia |
E66213
|
entity |
| Predicate | unificationCentury |
P10303
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Mazovia, unificationCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationCentury Context triple: [Mazovia, unificationCentury, 16th century]
-
A.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
B.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
C.
century
chosen
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
D.
dynasticUnion
Indicates a political relationship in which two or more distinct states are ruled by the same dynasty or monarch while formally remaining separate entities.
-
E.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada643e3e481908f4526d66e36e150 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.