Triple

T28390909
Position Surface form Disambiguated ID Type / Status
Subject WSearch E719152 entity
Predicate configurableOption P86411 FINISHED
Object indexed locations 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: indexed locations | Statement: [WSearch, configurableOption, indexed locations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: configurableOption
Context triple: [WSearch, configurableOption, indexed locations]
  • A. configurationOptionIn
    Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
  • B. constraintOption
    Indicates that one entity represents a specific selectable option or value that can be chosen to satisfy or configure a constraint imposed by another entity.
  • C. configurableProperty chosen
    Indicates that an entity has a setting or attribute whose value can be adjusted or customized, typically to modify its behavior or characteristics.
  • D. optionedBy
    Indicates that the rights to develop, produce, or exploit something (such as a work, property, or asset) have been contractually secured by a particular party.
  • E. customizableBy
    Indicates that one entity can be modified, configured, or tailored in some way by 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_69eff6ef211081909d31d9be5f5567e6 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f6afebd7ec8190ab696f363d84abf0 completed May 3, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69f6aca204148190850a3dc325bc07b7 completed May 3, 2026, 2:02 a.m.
Created at: April 28, 2026, 1:13 a.m.