Triple

T22876666
Position Surface form Disambiguated ID Type / Status
Subject Mozilla Public License E567343 entity
Predicate hasLiabilityLimitation P99 FINISHED
Object yes 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: yes | Statement: [Mozilla Public License, hasLiabilityLimitation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLiabilityLimitation
Context triple: [Mozilla Public License, hasLiabilityLimitation, yes]
  • A. carrierLiabilityLimitBasis
    Indicates the basis or standard used to determine the maximum liability amount a carrier is responsible for in case of loss, damage, or claim.
  • B. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • C. statutoryLimitPerIncidentUSD
    Indicates the maximum monetary amount, in U.S. dollars, that is legally allowed to be claimed or paid for a single incident under a specific statute or regulation.
  • D. liabilityType
    Indicates the specific category or nature of liability associated with an entity, obligation, or financial exposure.
  • E. hasLiabilityDisclaimer
    Indicates that an entity includes or is associated with a statement limiting or excluding legal responsibility for certain actions, outcomes, or information.
  • 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f58a7308190b710bdf013e2e114 completed April 29, 2026, 3:47 a.m.
PD Predicate disambiguation batch_69eed2d8c0608190afef4c4e530c0e2c completed April 27, 2026, 3:07 a.m.
Created at: April 17, 2026, 3:39 p.m.