Triple

T17675552
Position Surface form Disambiguated ID Type / Status
Subject Active Job E440633 entity
Predicate supportsQueueAdapters P127917 FINISHED
Object symbol-based adapter configuration 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: symbol-based adapter configuration | Statement: [Active Job, supportsQueueAdapters, symbol-based adapter configuration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsQueueAdapters
Context triple: [Active Job, supportsQueueAdapters, symbol-based adapter configuration]
  • A. usesQueue
    Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
  • B. supportsAgents
    Indicates that one entity provides assistance, resources, or backing to agents so they can perform their roles or actions.
  • C. alsoSupports chosen
    Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
  • D. supportedFleet
    Indicates that one entity provided assistance, resources, or services to sustain or enable the operations of a fleet.
  • E. supportsAt
    Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
  • 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6cca54819094ea0bed1517724e completed April 19, 2026, 6 a.m.
PD Predicate disambiguation batch_69e3cde007d8819090dd92eea9f022cc completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 10 a.m.