Triple
T7894859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COM |
E183319
|
entity |
| Predicate | enables |
P273
|
FINISHED |
| Object | COM+ services |
E183322
|
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: COM+ services | Statement: [COM, enables, COM+ services]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: COM+ services Context triple: [COM, enables, COM+ services]
-
A.
COM+
chosen
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.
-
B.
DCOM
DCOM (Distributed Component Object Model) is a Microsoft technology that extends COM to support communication among software components over a network, enabling distributed, component-based applications.
-
C.
.NET Remoting
.NET Remoting is a now-legacy Microsoft .NET framework technology that enabled communication and object interaction across application domains, processes, and network boundaries.
-
D.
FreeCOM
FreeCOM is the default command-line interpreter (command.com replacement) used by the FreeDOS operating system.
-
E.
Windows Communication Foundation
Windows Communication Foundation is a Microsoft framework for building and running service-oriented, distributed applications that communicate over various network protocols.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a15a7e88190a05474844817e5d2 |
completed | March 31, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdfc1b05481908af081f54bb1914d |
completed | March 31, 2026, 2:52 p.m. |
Created at: March 30, 2026, 5:01 p.m.