Triple

T26378107
Position Surface form Disambiguated ID Type / Status
Subject Altera HardCopy family E660952 entity
Predicate migrationPathFrom P36610 FINISHED
Object Altera FPGAs 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: Altera FPGAs | Statement: [Altera HardCopy family, migrationPathFrom, Altera FPGAs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: migrationPathFrom
Context triple: [Altera HardCopy family, migrationPathFrom, Altera FPGAs]
  • A. migrationFrom chosen
    Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
  • B. migrationPattern
    Indicates the typical routes, timing, and destinations followed by entities as they move periodically from one location or region to another.
  • C. migrationLink
    Indicates a relationship where one entity moves, transitions, or is transferred from one context, location, or system to another.
  • D. migrationProgram
    Indicates that there is a structured plan or scheme designed to manage, support, or regulate the movement or relocation of entities from one place or system to another.
  • E. migrationPolicy
    Indicates the rules or strategies governing how entities move, transfer, or transition from one context, location, or state to 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_69ee812a698881908d6a58265995fa39 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f6430a93a48190854ce71df680b2fa completed May 2, 2026, 6:31 p.m.
PD Predicate disambiguation batch_69f641da05b881909f6283c988639c53 completed May 2, 2026, 6:26 p.m.
Created at: April 26, 2026, 11:02 p.m.