Triple

T1676956
Position Surface form Disambiguated ID Type / Status
Subject L86 LSW E36251 entity
Predicate standardOptic P7239 FINISHED
Object SUIT/ SUSAT optical sight (earlier service) 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: SUIT/ SUSAT optical sight (earlier service) | Statement: [L86 LSW, standardOptic, SUIT/ SUSAT optical sight (earlier service)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardOptic
Context triple: [L86 LSW, standardOptic, SUIT/ SUSAT optical sight (earlier service)]
  • A. usesOpticsType chosen
    Indicates that one entity employs or is characterized by a specific type of optical system or technology.
  • B. opticalDesign
    Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
  • C. originalLens
    Indicates that one lens is the initial or source lens from which another lens or lens configuration is derived or referenced.
  • D. standardState
    Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
  • E. standardType
    Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
  • 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_69a886139ed081909af0940aa9313512 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab272a653481908f48aa1eed5de8a4 completed March 6, 2026, 7:12 p.m.
PD Predicate disambiguation batch_69aa61b2f6288190b2348ef7d7e4672d completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:29 p.m.