Triple

T27708671
Position Surface form Disambiguated ID Type / Status
Subject Internal Revenue Code Section 402(g) E698618 entity
Predicate isIndexedFor P163107 FINISHED
Object cost-of-living adjustments 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: cost-of-living adjustments | Statement: [Internal Revenue Code Section 402(g), isIndexedFor, cost-of-living adjustments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isIndexedFor
Context triple: [Internal Revenue Code Section 402(g), isIndexedFor, cost-of-living adjustments]
  • A. hasIndexing
    Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
  • B. canIndex
    Indicates that one entity has the capability or permission to create, maintain, or use an index over another entity (such as data, documents, or resources) for efficient access or retrieval.
  • C. usedInIndex
    Indicates that something is utilized or referenced within a particular index or indexing structure.
  • D. indexed
    Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
  • E. usesIndexation
    Indicates that one entity applies or relies on an indexing scheme or index-based method provided by or associated with another entity.
  • F. None of above. chosen

Provenance (4 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_69ef590f655c81909f93893b3b3219b2 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f63639a84c81909d700a539b458b42 completed May 2, 2026, 5:36 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 3:01 p.m.