Triple

T6800212
Position Surface form Disambiguated ID Type / Status
Subject 金本知憲 E156163 entity
Predicate 連続フルイニング出場世界記録保持者 P29425 FINISHED
Object はい 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: はい | Statement: [金本知憲, 連続フルイニング出場世界記録保持者, はい]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 連続フルイニング出場世界記録保持者
Context triple: [金本知憲, 連続フルイニング出場世界記録保持者, はい]
  • A. isAllTimeRecordHolderFor chosen
    Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
  • B. franchiseRecordHeld
    Indicates that one entity holds or possesses a record or achievement within the context of a particular franchise.
  • C. wasWorldRecordFor
    Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
  • D. hasWorldChampionship
    Indicates that an entity possesses, has won, or holds a world championship title or status.
  • E. heldWorldsLargestTitleUntil
    Indicates that an entity held the distinction of being the world’s largest in a particular category up to a specified point in time.
  • 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_69c6881844448190a65822d9b39d7f88 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d2e457408190a0ad9b0c48d8147c completed March 27, 2026, 6:56 p.m.
PD Predicate disambiguation batch_69c6d099bf08819089a9f9894d037e74 completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:15 p.m.