Triple

T32708568
Position Surface form Disambiguated ID Type / Status
Subject SecurityContext API E836337 entity
Predicate belongsToSpecification P103780 FINISHED
Object Jakarta Security specification NE NERFINISHED

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: Jakarta Security specification | Statement: [SecurityContext API, belongsToSpecification, Jakarta Security specification]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: belongsToSpecification
Context triple: [SecurityContext API, belongsToSpecification, Jakarta Security specification]
  • A. relatedToSpecification chosen
    Indicates that something has a connection or relevance to a particular specification, standard, or set of defined requirements.
  • B. belongsToPattern
    Indicates that something is a component, instance, or member of a specified pattern or structured template.
  • C. belongsToFeature
    Indicates that one entity is a component, attribute, or part of a larger feature or functionality associated with another entity.
  • D. belongsToColumn
    Indicates that one entity is a member or element of a specific column within a structured table or dataset.
  • E. belongsToStyle
    Indicates that something is associated with, classified under, or part of a particular style or stylistic category.
  • 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_69f3493446148190819541f3ffe79975 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fedfd913f48190bdcd450980868d9a completed May 9, 2026, 7:18 a.m.
PD Predicate disambiguation batch_69fedf58c6e88190821a7156054c9086 completed May 9, 2026, 7:16 a.m.
Created at: May 1, 2026, 1:10 a.m.