Triple

T10434698
Position Surface form Disambiguated ID Type / Status
Subject Government of Lithuania E246007 entity
Predicate re-establishedIn P9113 FINISHED
Object 1990 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: 1990 | Statement: [Government of Lithuania, re-establishedIn, 1990]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: re-establishedIn
Context triple: [Government of Lithuania, re-establishedIn, 1990]
  • A. re-establishedAfter
    Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
  • B. reincorporated
    Indicates that an entity has been formed again or brought back into existence as a corporation after having previously ceased or changed its corporate status.
  • C. reconstructedIn
    Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
  • D. reestablishedInYear chosen
    Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
  • E. reintroduced
    Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea67344c81909984ab99b0ef1e64 completed April 7, 2026, 11:28 a.m.
PD Predicate disambiguation batch_69d4dfbc546881908f312c66ee195f79 completed April 7, 2026, 10:43 a.m.
Created at: April 6, 2026, 12:14 p.m.