Triple

T6328025
Position Surface form Disambiguated ID Type / Status
Subject Analytical Engine E141905 entity
Predicate anticipatedConcept P201 FINISHED
Object general-purpose computer 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: general-purpose computer | Statement: [Analytical Engine, anticipatedConcept, general-purpose computer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: anticipatedConcept
Context triple: [Analytical Engine, anticipatedConcept, general-purpose computer]
  • A. anticipates
    Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
  • B. featuredConcept
    Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
  • C. introducedConcept chosen
    Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
  • D. hasPlanningConcept
    Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
  • E. predictedIn
    Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
  • 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_69c008d201748190917e69c41ba3f978 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c064e9532081908277f10ec380a486 completed March 22, 2026, 9:53 p.m.
PD Predicate disambiguation batch_69c060e7e2d48190af9d004236466788 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:29 p.m.