Triple

T26966758
Position Surface form Disambiguated ID Type / Status
Subject NL E679191 entity
Predicate notKnownToBeClosedUnder P161389 FINISHED
Object complement 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: complement | Statement: [NL, notKnownToBeClosedUnder, complement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notKnownToBeClosedUnder
Context triple: [NL, notKnownToBeClosedUnder, complement]
  • A. notClosedUnder
    Indicates that applying the operation or relation to elements of a set can produce results that do not belong to that set, so the set is not closed under that operation or relation.
  • B. notOpenAs
    Indicates that one entity is explicitly not used, treated, or interpreted in the role, format, or capacity specified by another entity.
  • C. lineClosedUnder
    Indicates that a given line is closed under a specified operation, meaning applying the operation to any elements on the line produces a result that also lies on the same line.
  • D. closedFor
    Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
  • E. subjectToClosure
    Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
  • 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_69eeeb4f3a448190b1e94b2d4776c16e completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f621210b788190ab9e910cd635f366 completed May 2, 2026, 4:06 p.m.
PD Predicate disambiguation batch_69f611af72ac819094598dd2530d7411 completed May 2, 2026, 3:01 p.m.
PDg Predicate description generation batch_69f6125e54e0819088ee33a20efcc9e6 completed May 2, 2026, 3:03 p.m.
Created at: April 27, 2026, 6:36 a.m.