Triple
T9443428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | registered association (eingetragener Verein) |
E227703
|
entity |
| Predicate | mustUseAssetsFor |
P88219
|
FINISHED |
| Object | statutory 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: statutory purposes | Statement: [registered association (eingetragener Verein), mustUseAssetsFor, statutory purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustUseAssetsFor Context triple: [registered association (eingetragener Verein), mustUseAssetsFor, statutory purposes]
-
A.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
-
B.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
C.
mustTouch
Indicates that the entities are required to be in direct physical contact with each other.
-
D.
mayRequireComponent
Indicates that one entity can optionally depend on or need another entity as a component for its proper use or operation.
-
E.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
- 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_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. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:51 p.m.