Triple
T11958655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNATmake |
E284614
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | GNAT |
E59598
|
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: GNAT | Statement: [GNATmake, partOf, GNAT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GNAT Context triple: [GNATmake, partOf, GNAT]
-
A.
GNAT Pro Enterprise
GNAT Pro Enterprise is AdaCore’s professional-grade Ada and SPARK development environment designed for building high-assurance, safety- and mission-critical software systems.
-
B.
GNAT Studio
GNAT Studio is an integrated development environment (IDE) by AdaCore designed primarily for developing, debugging, and maintaining Ada and mixed-language software systems.
-
C.
gnat
chosen
GNAT is a free, open-source Ada compiler and toolchain that is part of the GNU Compiler Collection (GCC).
-
D.
AdaCore
AdaCore is a software company specializing in high-integrity, safety- and security-critical development tools and compilers for the Ada programming language.
-
E.
GNAT Pro Assurance
GNAT Pro Assurance is a high-reliability, safety- and security-focused Ada development and verification tool suite from AdaCore used for long-term, certifiable software projects in critical domains.
- 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_69f61e391d7c8190a414cb3306bfe139 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:45 p.m.