Triple

T26176921
Position Surface form Disambiguated ID Type / Status
Subject ColecoVision E654566 entity
Predicate expansionModule3Function P117270 FINISHED
Object ADAM computer expansion 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: ADAM computer expansion | Statement: [ColecoVision, expansionModule3Function, ADAM computer expansion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: expansionModule3Function
Context triple: [ColecoVision, expansionModule3Function, ADAM computer expansion]
  • A. expansionSystem
    Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
  • B. expansionUnit chosen
    Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
  • C. expansionProject
    Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
  • D. expansionAdded
    Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
  • E. expansionNumber
    Indicates the specific expansion sequence or identifier assigned to an entity within a series of related additions or extensions.
  • 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_69ee5b45873c81909499203612d05d07 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 26, 2026, 8:38 p.m.