Triple

T9443424
Position Surface form Disambiguated ID Type / Status
Subject registered association (eingetragener Verein) E227703 entity
Predicate canBeRecognizedAs P76859 FINISHED
Object charitable (gemeinnützig) for tax purposes — 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: charitable (gemeinnützig) for tax purposes | Statement: [registered association (eingetragener Verein), canBeRecognizedAs, charitable (gemeinnützig) for tax purposes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeRecognizedAs
Context triple: [registered association (eingetragener Verein), canBeRecognizedAs, charitable (gemeinnützig) for tax purposes]
  • A. canRecognize
    Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
  • B. areRecognizedBy
    Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
  • C. recognizedAs
    Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
  • D. canBeViewedAs chosen
    Indicates that one entity may be interpreted, treated, or understood as another entity or type under some perspective or conditions.
  • E. resultRecognizedBy
    Indicates that a particular result is formally acknowledged, validated, or accepted by a specified recognizing entity.
  • 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_69ca843884488190ad6cbe0153088234 completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7f3171248190b92ab990371e63f5 completed April 1, 2026, 8:25 p.m.
PD Predicate disambiguation batch_69cca5596ffc819097e9c8eefd4ef9b8 completed April 1, 2026, 4:55 a.m.
Created at: March 30, 2026, 7:51 p.m.