Triple
T34902396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lodomeria |
E1006626
|
entity |
| Predicate | historicalClaimOver |
P89298
|
FINISHED |
| Object | parts of Volhynia |
—
|
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: parts of Volhynia | Statement: [Lodomeria, historicalClaimOver, parts of Volhynia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalClaimOver Context triple: [Lodomeria, historicalClaimOver, parts of Volhynia]
-
A.
historicalClaimBy
Indicates that a particular historical assertion or interpretation is attributed to a specific source or agent.
-
B.
historicalClaim
Indicates that an entity asserts or presents a statement about past events or conditions as a matter of historical fact.
-
C.
historicallyClaimedBy
chosen
Indicates that an entity has, at some point in the past, asserted ownership, control, or rights over another entity or territory.
-
D.
heritageClaimedBy
Indicates that a particular heritage, tradition, or cultural legacy is asserted or identified as belonging to a specific entity.
-
E.
laterClaimedToBe
Indicates that an entity asserted or stated something at a later time than the original event or statement.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4 p.m.