Triple
T33469088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Lithuania (1918–1940) |
E857137
|
entity |
| Predicate | hadDisputeOver |
P28645
|
FINISHED |
| Object | Vilnius Region |
—
|
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: Vilnius Region | Statement: [Republic of Lithuania (1918–1940), hadDisputeOver, Vilnius Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadDisputeOver Context triple: [Republic of Lithuania (1918–1940), hadDisputeOver, Vilnius Region]
-
A.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
B.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
C.
hasDisputedStatusWith
chosen
Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
-
D.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
E.
hasDisputedClause
Indicates that a particular clause within an agreement or document is subject to disagreement, challenge, or contention between involved parties.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4fcba588190a8f812723270d6ba |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.