Triple

T22876629
Position Surface form Disambiguated ID Type / Status
Subject SeaMonkey Council E567342 entity
Predicate governsLicense P107527 FINISHED
Object SeaMonkey open-source licensing 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: SeaMonkey open-source licensing | Statement: [SeaMonkey Council, governsLicense, SeaMonkey open-source licensing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governsLicense
Context triple: [SeaMonkey Council, governsLicense, SeaMonkey open-source licensing]
  • A. legalLicenseIn
    Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
  • B. oftenLicensedUnder
    Indicates that an entity is frequently or commonly granted rights or permissions under a specified license.
  • C. licenseFocus
    Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
  • D. basedOnLicense chosen
    Indicates that one entity is derived from, uses, or is governed by the terms of another entity’s license.
  • E. licenseStewardship
    Indicates that one entity is responsible for managing, overseeing, or administering a license on behalf of another 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_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.