Triple
T38084482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiftung des bürgerlichen Rechts |
E950937
|
entity |
| Predicate | liability |
P181596
|
FINISHED |
| Object | liable with its foundation assets |
—
|
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: liable with its foundation assets | Statement: [Stiftung des bürgerlichen Rechts, liability, liable with its foundation assets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liability Context triple: [Stiftung des bürgerlichen Rechts, liability, liable with its foundation assets]
-
A.
liabilityType
Indicates the specific category or nature of liability associated with an entity, obligation, or financial exposure.
-
B.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
C.
liabilityContext
chosen
Indicates the situational or legal circumstances under which liability arises, is assessed, or applies between entities.
-
D.
modeOfLiability
Indicates the specific legal basis or manner in which an entity is held responsible for an act or outcome.
-
E.
recallLiability
Indicates a relationship where an entity bears legal or financial responsibility for initiating or managing a product recall.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.