Triple

T25371959
Position Surface form Disambiguated ID Type / Status
Subject Glushkov construction E632952 entity
Predicate typicalOutputAutomaton P66288 FINISHED
Object position automaton of the given regular expression 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: position automaton of the given regular expression | Statement: [Glushkov construction, typicalOutputAutomaton, position automaton of the given regular expression]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOutputAutomaton
Context triple: [Glushkov construction, typicalOutputAutomaton, position automaton of the given regular expression]
  • A. producesAutomatonWith
    Indicates that one entity creates or generates an automaton that is associated with or used by another entity.
  • B. typicalStateSpace
    Indicates the usual or standard set of states in which an entity, system, or process is considered to operate.
  • C. outputOf chosen
    Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
  • D. actorOutputs
    Indicates that an actor produces or emits certain outputs as a result of its actions or behavior.
  • E. outputsTo
    Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
  • 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_69e75a90c0dc819092f928b6ea0ecc72 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69fd0b92f42881908cd77e3f058adcc2 completed May 7, 2026, 10 p.m.
PD Predicate disambiguation batch_69fd0a3d68d4819094d92040f7c48d7c completed May 7, 2026, 9:55 p.m.
Created at: April 21, 2026, 1:38 p.m.