Triple

T7694459
Position Surface form Disambiguated ID Type / Status
Subject Myers–Briggs Type Indicator E174334 entity
Predicate usesScoring P48244 FINISHED
Object preference clarity indices 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: preference clarity indices | Statement: [Myers–Briggs Type Indicator, usesScoring, preference clarity indices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesScoring
Context triple: [Myers–Briggs Type Indicator, usesScoring, preference clarity indices]
  • A. scoring
    Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
  • B. scoreUsedFor
    Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
  • C. usesCompositeScore
    Indicates that an entity bases its evaluation, decision, or outcome on a combined score derived from multiple underlying metrics or factors.
  • D. scoringType chosen
    Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
  • E. isScoreFor
    Indicates that one value represents the score or result associated with a particular entity, event, or performance.
  • 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_69c6995966348190939e6c37ba272c06 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c706d1f0208190bc5b695aa5736244 completed March 27, 2026, 10:38 p.m.
PD Predicate disambiguation batch_69c70163dea88190ae729df50e63dfd7 completed March 27, 2026, 10:15 p.m.
Created at: March 27, 2026, 4:02 p.m.