Triple

T35736831
Position Surface form Disambiguated ID Type / Status
Subject Unisys Corporation E1032910 entity
Predicate followsAccountingStandard P44307 FINISHED
Object US GAAP NE NERFINISHED

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: US GAAP | Statement: [Unisys Corporation, followsAccountingStandard, US GAAP]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: followsAccountingStandard
Context triple: [Unisys Corporation, followsAccountingStandard, US GAAP]
  • A. reportingStandard chosen
    Indicates that one entity uses, follows, or is governed by a particular reporting standard defined by another entity.
  • B. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • C. accrualMethod
    Indicates the method or basis by which something (such as interest, revenue, or benefits) is accumulated or recognized over time.
  • D. usedForAccounting
    Indicates that something is employed in performing, supporting, or managing accounting activities or financial record-keeping.
  • E. accountingTreatment
    Indicates how a transaction, event, or item is recognized, measured, and reported in financial accounts according to specific accounting rules or policies.
  • 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_69f76e10e59081908d81ad9ce22f40b6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff1ba8694481909ceb36f26ca85612 completed May 9, 2026, 11:34 a.m.
PD Predicate disambiguation batch_69ff1b27f0f08190a9e74308c5b3d1ba completed May 9, 2026, 11:31 a.m.
Created at: May 3, 2026, 4:05 p.m.