Triple

T8227274
Position Surface form Disambiguated ID Type / Status
Subject Corfinium E192202 entity
Predicate mentionedBy P831 FINISHED
Object Appian E212508 NE 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: Appian | Statement: [Corfinium, mentionedBy, Appian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Appian
Context triple: [Corfinium, mentionedBy, Appian]
  • A. Appian chosen
    Appian was a 2nd-century AD Roman historian of Greek origin best known for his multi-volume work "Roman History," which includes a detailed account of the Roman civil wars.
  • B. Appirio
    Appirio is a cloud services and consulting company known for helping enterprises implement and optimize platforms like Salesforce and Workday.
  • C. Zoho Creator
    Zoho Creator is a low-code application development platform that enables users to quickly build and deploy custom business apps with minimal programming.
  • D. Zoho Projects
    Zoho Projects is a cloud-based project management and collaboration tool designed to help teams plan, track, and deliver projects efficiently.
  • E. Zoho Flow
    Zoho Flow is a cloud-based integration and workflow automation platform that lets users connect apps and automate business processes without coding.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca82db5b90819085d1ad7c2e27bfcc completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb77fdcb048190868ea4995b020a37 completed March 31, 2026, 7:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd34d4b6ec81909bc5d23bad1f326b completed April 1, 2026, 3:08 p.m.
Created at: March 30, 2026, 5:46 p.m.