Triple
T23154470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Theia |
E578402
|
entity |
| Predicate | supportsStandard |
P1587
|
FINISHED |
| Object | Debug Adapter Protocol |
—
|
NE NERFINISHED |
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: Debug Adapter Protocol | Statement: [Eclipse Theia, supportsStandard, Debug Adapter Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Debug Adapter Protocol Context triple: [Eclipse Theia, supportsStandard, Debug Adapter Protocol]
-
A.
Debug Adapter Protocol
chosen
The Debug Adapter Protocol is an open standard that defines a common interface between development tools and debuggers, enabling consistent debugging experiences across different editors, IDEs, and languages.
-
B.
LLDB
LLDB is a modern, high-performance debugger primarily used with the LLVM toolchain for languages like C, C++, and Objective-C.
-
C.
Turbo Debugger
Turbo Debugger is a DOS-based source-level debugger from Borland, commonly used alongside Turbo C++ for debugging C and C++ programs.
-
D.
Java Debug Wire Protocol
Java Debug Wire Protocol is a low-level, packet-based communication protocol used by Java debuggers to interact with and control a running Java Virtual Machine during debugging sessions.
-
E.
Chrome DevTools Protocol
Chrome DevTools Protocol is a low-level, JSON-based debugging and automation interface used to inspect, instrument, and control Chromium-based browsers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efbe9a08190bcb6e822b8eab544 |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:01 p.m.