Triple
T3166036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazovia |
E66213
|
entity |
| Predicate | wasPiastTerritory |
P13519
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mazovia, wasPiastTerritory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPiastTerritory Context triple: [Mazovia, wasPiastTerritory, yes]
-
A.
wasProtectorateOf
Indicates that one entity was formerly under the protection and partial control of another, typically more powerful, entity.
-
B.
wasCoreTerritoryOf
chosen
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
C.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
D.
wasAnnexedInPartition
Indicates that a territory or entity was incorporated into another as a result of a formal partition of land or political division.
-
E.
wasExclaveOf
Indicates that a territory or region was geographically separated from its main governing state and politically belonged to that state as an exclave.
- 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.