Triple
T11958615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AdaCore |
E284613
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | CodePeer |
E955083
|
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: CodePeer | Statement: [AdaCore, product, CodePeer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CodePeer Context triple: [AdaCore, product, CodePeer]
-
A.
Static Code Checker
chosen
Static Code Checker is a software tool that automatically analyzes source code without executing it to detect bugs, security vulnerabilities, and style or quality issues.
-
B.
Checkmarx
Checkmarx is a cybersecurity company specializing in application security testing solutions that help organizations identify and remediate vulnerabilities in their software code.
-
C.
Helix Swarm code review tool
Helix Swarm is Perforce’s web-based code review and collaboration tool designed to streamline peer reviews, improve code quality, and integrate tightly with Helix Core version control.
-
D.
dotCover
dotCover is a .NET unit test runner and code coverage tool designed to help developers measure and improve test coverage in Visual Studio.
-
E.
Clang-Tidy
Clang-Tidy is a C++ “linter” and static analysis tool that automatically detects and suggests fixes for common programming errors, style issues, and potential bugs in code.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f459210d1c8190953cd01da3d2ad04 |
completed | May 1, 2026, 7:41 a.m. |
Created at: April 8, 2026, 9:45 p.m.