Triple
T29388140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluetooth Core Specification |
E745304
|
entity |
| Predicate | definesVersioning |
P87767
|
FINISHED |
| Object | Bluetooth version numbers |
—
|
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: Bluetooth version numbers | Statement: [Bluetooth Core Specification, definesVersioning, Bluetooth version numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesVersioning Context triple: [Bluetooth Core Specification, definesVersioning, Bluetooth version numbers]
-
A.
definesVersionOf
chosen
Indicates that one entity specifies or establishes the version or variant identity of another entity.
-
B.
versioningModel
Indicates that one entity serves as a versioning or revision-control model governing how versions of another entity are created, tracked, and managed.
-
C.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
D.
versionedAs
Indicates that one entity exists as a specific version or revision of another entity.
-
E.
versioningRule
Indicates the rule or policy that governs how different versions of an entity are created, labeled, and managed over 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 28, 2026, 2:40 p.m.