Triple

T15336668
Position Surface form Disambiguated ID Type / Status
Subject Ingrian language E366683 entity
Predicate historicalPressureFrom P118164 FINISHED
Object Russian language 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: Russian language | Statement: [Ingrian language, historicalPressureFrom, Russian language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalPressureFrom
Context triple: [Ingrian language, historicalPressureFrom, Russian language]
  • A. historicalPressure
    Indicates a relationship where past events, traditions, or long-standing expectations exert influence or constraint on an entity’s current decisions, behavior, or state.
  • B. historicalValue
    Indicates that something possesses significance, importance, or relevance due to its connection with past events, periods, or developments.
  • C. historicalPass
    Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
  • D. historicalDatum
    Indicates that something is a specific piece of information or record about a past event, condition, or state.
  • E. historicalPeak
    Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
  • F. None of above. chosen

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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e11b22c81908280efe65acd5454 completed April 16, 2026, 1:40 a.m.
PD Predicate disambiguation batch_69deca9659f48190b8661df223ce5078 completed April 14, 2026, 11:15 p.m.
PDg Predicate description generation batch_69decf2e413481909d9180a8d78d2c17 completed April 14, 2026, 11:35 p.m.
Created at: April 10, 2026, 3:17 a.m.