Triple
T32167859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan Tadeusz |
E821626
|
entity |
| Predicate | setInHistoricalRegion |
P55801
|
FINISHED |
| Object | Grand Duchy of Lithuania |
E59761
|
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: Grand Duchy of Lithuania | Statement: [Pan Tadeusz, setInHistoricalRegion, Grand Duchy of Lithuania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInHistoricalRegion Context triple: [Pan Tadeusz, setInHistoricalRegion, Grand Duchy of Lithuania]
-
A.
isInHistoricRegion
chosen
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
B.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
C.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
D.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
-
E.
historicalOperationRegion
Indicates the geographic area in which an entity carried out its activities or operations during a past or historical period.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3056eda90c819096c0245cc3bdc986 |
completed | June 15, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:33 a.m.