Triple
T5313992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aktiengesellschaft |
E119100
|
entity |
| Predicate | hasLiabilityType |
P58861
|
FINISHED |
| Object | limited liability |
—
|
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: limited liability | Statement: [Aktiengesellschaft, hasLiabilityType, limited liability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiabilityType Context triple: [Aktiengesellschaft, hasLiabilityType, limited liability]
-
A.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
B.
carrierLiabilityType
chosen
Indicates the specific type or category of legal or contractual liability that a carrier assumes in relation to the goods or services it transports or provides.
-
C.
obligationType
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
D.
typeOfDiscriminationCovered
Indicates that a particular kind or category of discriminatory behavior is included within the scope of protections, rules, or analysis.
-
E.
hasWealthType
Indicates that an entity possesses or is associated with a particular category or type of wealth.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:54 p.m.