Triple

T4293669
Position Surface form Disambiguated ID Type / Status
Subject A3C E99656 entity
Predicate usesParallelAgents P34884 FINISHED
Object multiple parallel workers 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: multiple parallel workers | Statement: [A3C, usesParallelAgents, multiple parallel workers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesParallelAgents
Context triple: [A3C, usesParallelAgents, multiple parallel workers]
  • A. isParallelizable chosen
    Indicates that a process, task, or operation can be decomposed into independent parts that may be executed concurrently without affecting correctness.
  • B. hasParallelReporter
    Indicates that a legal case or decision has an alternative citation or report in a different reporter series that runs in parallel to the primary one.
  • C. followsParallel
    Indicates that one entity proceeds in the same general direction or sequence as another, maintaining a parallel course or progression without necessarily intersecting.
  • D. hasParallelBody
    Indicates that one entity’s body is oriented in a direction parallel to the body of another entity.
  • E. hasParallelTransit
    Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
  • 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_69b3455175088190aa79c6e03b86647e completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35082228081908504e3fd7c4ca1e8 completed March 12, 2026, 11:47 p.m.
PD Predicate disambiguation batch_69b347fe55a88190b77bab0c0f38e1aa completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:08 p.m.