Triple

T4214264
Position Surface form Disambiguated ID Type / Status
Subject Honda CR-V E93974 entity
Predicate salesRank P51791 FINISHED
Object one of the best-selling SUVs worldwide 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: one of the best-selling SUVs worldwide | Statement: [Honda CR-V, salesRank, one of the best-selling SUVs worldwide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: salesRank
Context triple: [Honda CR-V, salesRank, one of the best-selling SUVs worldwide]
  • A. SSRank
    Indicates a ranking relationship that orders entities based on their social status, standing, or relative importance within a specified context.
  • B. bestsellingStatus chosen
    Indicates that an item has achieved a high sales ranking or volume, typically qualifying it as a “bestseller” within a defined market or category.
  • C. rankedBy
    Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
  • D. rankedAs
    Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
  • E. usesRank
    Indicates that one entity applies or relies on a ranking or ordered level system associated with 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_69b3451743608190808f41d17ccf2650 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34e098da881909a0cc339cc186627 completed March 12, 2026, 11:36 p.m.
PD Predicate disambiguation batch_69b347efd9b08190bb50f82e4e7fe06d completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:04 p.m.