Triple

T12679364
Position Surface form Disambiguated ID Type / Status
Subject Common Admission Test E302904 entity
Predicate competitiveness P16079 FINISHED
Object highly competitive 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: highly competitive | Statement: [Common Admission Test, competitiveness, highly competitive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competitiveness
Context triple: [Common Admission Test, competitiveness, highly competitive]
  • A. competition
    Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
  • B. competitiveDiscipline
    Indicates a relationship where an entity participates in or is associated with a structured, rule-based activity or field in which individuals or groups compete against each other.
  • C. isCompetitive
    Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
  • D. competitiveEffect
    Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
  • E. competitiveContext chosen
    Indicates a situation in which entities are engaged in or influenced by competition with one another.
  • 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_69d7bdee64a08190801c6d470aefd723 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961b1dff48190923290555ece5d89 completed April 10, 2026, 8:46 p.m.
PD Predicate disambiguation batch_69d960bb64ec8190bd0400cf0cc8b0a7 completed April 10, 2026, 8:42 p.m.
Created at: April 9, 2026, 5:21 p.m.