Triple

T27582796
Position Surface form Disambiguated ID Type / Status
Subject IBM Knowledge Center E699622 entity
Predicate documentationSourceFor P132738 FINISHED
Object official IBM product information 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: official IBM product information | Statement: [IBM Knowledge Center, documentationSourceFor, official IBM product information]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: documentationSourceFor
Context triple: [IBM Knowledge Center, documentationSourceFor, official IBM product information]
  • A. documentedFrom
    Indicates that information about one entity is derived from, recorded in, or supported by another entity as its source of documentation.
  • B. documentSource
    Indicates that one entity serves as the origin, provider, or provenance source for a given document.
  • C. documentationReference chosen
    Indicates that one entity serves as a documentation source or reference that explains, specifies, or supports another entity.
  • D. documentationLocation
    Indicates the place or resource where relevant documentation for an entity can be found.
  • E. sourceDescribedBy
    Indicates that a source is documented, characterized, or otherwise explained by a particular description or descriptive resource.
  • 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_69ef6a4cb8b881909b3a8d630fd89df2 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f643ed0b7481908cf25f3afec0a61d completed May 2, 2026, 6:35 p.m.
PD Predicate disambiguation batch_69f641dc8ff48190ab575d855616580c completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 2:03 p.m.