Triple

T27850943
Position Surface form Disambiguated ID Type / Status
Subject Jet Database Engine E703949 entity
Predicate supportsConcurrencyControl P169394 FINISHED
Object record-level locking 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: record-level locking | Statement: [Jet Database Engine, supportsConcurrencyControl, record-level locking]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsConcurrencyControl
Context triple: [Jet Database Engine, supportsConcurrencyControl, record-level locking]
  • A. concurrencyControl chosen
    Indicates that multiple operations or transactions are coordinated so they can occur at the same time without interfering with each other or corrupting shared data.
  • B. hasConcurrency
    Indicates that two or more processes, tasks, or operations can occur or be executed simultaneously or with overlapping time intervals.
  • C. supportsConcurrentEditing
    Indicates that multiple users can edit the same item or resource at the same time without blocking one another.
  • D. supportsConcurrentModelExecution
    Indicates that one entity enables or allows multiple models to be executed at the same time without mutual interference.
  • E. requiresConcurrenceWith
    Indicates that one action, decision, or condition must be agreed upon or approved by another specified party or entity before it can proceed or be valid.
  • 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_69ef840e614c8190a88cf9638c14a265 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_6a001adc8c108190ab3a43f6415e2be3 completed May 10, 2026, 5:42 a.m.
PD Predicate disambiguation batch_6a001a290330819097c2c3123f9014b4 completed May 10, 2026, 5:39 a.m.
Created at: April 27, 2026, 6:10 p.m.