Triple

T37028312
Position Surface form Disambiguated ID Type / Status
Subject Ruby (gemstone) E916415 entity
Predicate historicalMisidentificationWith P10864 FINISHED
Object red spinel in crown jewels 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: red spinel in crown jewels | Statement: [Ruby (gemstone), historicalMisidentificationWith, red spinel in crown jewels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalMisidentificationWith
Context triple: [Ruby (gemstone), historicalMisidentificationWith, red spinel in crown jewels]
  • A. historicalIdentificationOf
    Indicates that one entity has been identified, classified, or recognized as another entity within a historical context or by historical sources.
  • B. associatedWithMisidentificationOf
    Indicates a relationship where one entity is connected to, or involved in, the incorrect identification or labeling of another entity.
  • C. misidentifiedAs
    Indicates that one entity has been incorrectly recognized, labeled, or understood as another, distinct entity.
  • D. historicallyConfusedWith chosen
    Indicates that one entity has been mistaken for or identified as another entity in historical records, interpretations, or traditions.
  • E. reasonForMisidentification
    Indicates the explanation or cause behind why one entity was incorrectly identified as 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_69f76e92c7648190bcfa277f64c71a21 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a017590e01c8190b985bb50cc6cd605 completed May 11, 2026, 6:22 a.m.
PD Predicate disambiguation batch_6a0175406b348190a5809b5f3497d46f completed May 11, 2026, 6:20 a.m.
Created at: May 3, 2026, 4:14 p.m.