Triple

T6595868
Position Surface form Disambiguated ID Type / Status
Subject WIPO Expert Determination Rules E148472 entity
Predicate canBeIncorporatedIn P5376 FINISHED
Object contracts 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: contracts | Statement: [WIPO Expert Determination Rules, canBeIncorporatedIn, contracts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeIncorporatedIn
Context triple: [WIPO Expert Determination Rules, canBeIncorporatedIn, contracts]
  • A. incorporatedAs
    Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
  • B. incorporatedThrough
    Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
  • C. canBeEmbeddedIn chosen
    Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
  • D. partiallyIncorporatedInto
    Indicates that one entity has been integrated or absorbed into another entity, but only to a limited or incomplete extent.
  • E. incorporatedAgainst
    Indicates that a legal entity was formally incorporated in opposition to, or as a countermeasure against, another party.
  • 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_69c687e7b8688190811ffee72e096468 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6cc9c6cb0819084fec8e0beb430de completed March 27, 2026, 6:29 p.m.
PD Predicate disambiguation batch_69c6acfd17388190bd0bb8b2371e7df1 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:55 p.m.