Triple

T25348978
Position Surface form Disambiguated ID Type / Status
Subject Heinrich Faust E635631 entity
Predicate dealCondition P133094 FINISHED
Object Mephistopheles serves Faust in life 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: Mephistopheles serves Faust in life | Statement: [Heinrich Faust, dealCondition, Mephistopheles serves Faust in life]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dealCondition
Context triple: [Heinrich Faust, dealCondition, Mephistopheles serves Faust in life]
  • A. conditionOfBargain chosen
    Indicates that one entity is a term, stipulation, or requirement that forms part of the agreed exchange in a bargain or contract.
  • B. dealContent
    Indicates that one entity contains, specifies, or represents the substantive terms, details, or material of a deal or agreement involving another entity.
  • C. conditionOfGoods
    Indicates the state, quality, or integrity that the goods are in at a given time or upon a specified event.
  • D. usedCondition
    Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
  • E. conditionOfOffer
    Indicates the terms, requirements, or circumstances under which an offer is valid or applies.
  • 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_69e75a9ac5d881909387ed766e20cd47 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f49dfa0e948190b98f6999963c7d55 completed May 1, 2026, 12:35 p.m.
PD Predicate disambiguation batch_69f45d0dbc8c8190beecce679fce90a4 completed May 1, 2026, 7:58 a.m.
Created at: April 21, 2026, 1:34 p.m.