Triple

T23961800
Position Surface form Disambiguated ID Type / Status
Subject Gastein Convention E603947 entity
Predicate considerationForTransfer P88040 FINISHED
Object financial payment by Prussia to Austria 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: financial payment by Prussia to Austria | Statement: [Gastein Convention, considerationForTransfer, financial payment by Prussia to Austria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: considerationForTransfer
Context triple: [Gastein Convention, considerationForTransfer, financial payment by Prussia to Austria]
  • A. consideredIn
    Indicates that one entity is taken into account, examined, or included as a factor within the context, scope, or decision framework of another entity.
  • B. mayBeTransferredIf
    Indicates that something is allowed to be transferred from one party or context to another under certain conditions.
  • C. transferReason chosen
    Indicates the reason or justification for a transfer occurring between entities.
  • D. transferable
    Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
  • E. considered
    Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
  • 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_69e2954222288190a7323554d0cca8d7 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d0dac8e081908286e8d8d30784ee completed April 29, 2026, 9:35 a.m.
PD Predicate disambiguation batch_69f161578d54819084a8b35496299993 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:23 p.m.