Triple
T26325328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Olza |
E662236
|
entity |
| Predicate | historicallyDisputedBy |
P2746
|
FINISHED |
| Object | Poland |
—
|
NE NERFINISHED |
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: Poland | Statement: [Trans-Olza, historicallyDisputedBy, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyDisputedBy Context triple: [Trans-Olza, historicallyDisputedBy, Poland]
-
A.
historicallyContestedBy
chosen
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
B.
historicallyContested
Indicates that the relationship or status between entities has been the subject of historical dispute, disagreement, or competing claims over time.
-
C.
historicallyContestedSince
Indicates that a subject has been the focus of dispute, disagreement, or contention starting from a specified point in time.
-
D.
historicalSovereigntyClaim
Indicates a relationship where an entity asserts that it held sovereign authority over another entity or territory at some point in the past.
-
E.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 26, 2026, 10:30 p.m.