Triple
T2561516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OLE DB |
E57250
|
entity |
| Predicate | usesTechnology |
P1485
|
FINISHED |
| Object | Component Object Model |
E183318
|
NE 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: Component Object Model | Statement: [OLE DB, usesTechnology, Component Object Model]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Component Object Model Context triple: [OLE DB, usesTechnology, Component Object Model]
-
A.
Component Object Model
chosen
Component Object Model (COM) is a Microsoft software architecture and binary-interface standard that enables interprocess communication and reusable software components across different programming languages.
-
B.
COM+
COM+ is a Microsoft component software technology that extends the Component Object Model (COM) with services like transactions, security, and object pooling to support scalable, distributed applications.
-
C.
Object Management Group
The Object Management Group is an international, nonprofit technology standards consortium best known for developing and maintaining widely used modeling and integration standards in software and systems engineering.
-
D.
Object Modeling Technique
Object Modeling Technique (OMT) is an early object-oriented analysis and design methodology that introduced structured notations for modeling systems, helping lay the groundwork for what became the Unified Modeling Language (UML).
-
E.
Objectory
Objectory is an object-oriented software development methodology created by Ivar Jacobson that introduced use cases and significantly shaped modern modeling approaches later incorporated into UML.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd336183c819084ed7de8ccc4c548 |
completed | March 7, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af5d233dbc81909feb1127cffb027f |
completed | March 9, 2026, 11:52 p.m. |
Created at: March 6, 2026, 9:48 p.m.