Triple
T18950673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardians and Actions: Linguistic Support for Robust, Distributed Programs |
E463638
|
entity |
| Predicate | influenced |
P9
|
FINISHED |
| Object | Argus programming language |
—
|
NE NERFINISHED |
How this triple was built (3 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: Argus programming language | Statement: [Guardians and Actions: Linguistic Support for Robust, Distributed Programs, influenced, Argus programming language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Argus programming language Context triple: [Guardians and Actions: Linguistic Support for Robust, Distributed Programs, influenced, Argus programming language]
-
A.
Odin programming language
Odin is a statically typed, compiled systems programming language focused on simplicity, data-oriented design, and high performance as an alternative to C.
-
B.
Vale programming language
Vale is a memory-safe, performance-focused systems programming language that explores region-based memory management and borrow-checking concepts similar to those in Rust.
-
C.
Cyclone programming language
Cyclone is a safe dialect of the C programming language designed to prevent common memory-management and type-safety errors while retaining low-level control and performance.
-
D.
Oberon programming language
The Oberon programming language is a minimalist, modular, and strongly typed language designed by Niklaus Wirth as the successor to Modula-2, emphasizing simplicity and efficiency in both language and operating system design.
-
E.
Fortress programming language
Fortress is a high-performance, mathematically oriented experimental programming language designed to explore parallelism and productivity in scientific and technical computing.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Argus programming language Target entity description: The Argus programming language is a distributed, object-based language developed at MIT in the 1980s to support robust, fault-tolerant distributed systems through integrated mechanisms for atomic transactions and guardians.
-
A.
Odin programming language
Odin is a statically typed, compiled systems programming language focused on simplicity, data-oriented design, and high performance as an alternative to C.
-
B.
Vale programming language
Vale is a memory-safe, performance-focused systems programming language that explores region-based memory management and borrow-checking concepts similar to those in Rust.
-
C.
Cyclone programming language
Cyclone is a safe dialect of the C programming language designed to prevent common memory-management and type-safety errors while retaining low-level control and performance.
-
D.
Oberon programming language
The Oberon programming language is a minimalist, modular, and strongly typed language designed by Niklaus Wirth as the successor to Modula-2, emphasizing simplicity and efficiency in both language and operating system design.
-
E.
Fortress programming language
Fortress is a high-performance, mathematically oriented experimental programming language designed to explore parallelism and productivity in scientific and technical computing.
- F. None of above. chosen
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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d542b238819089ccd2df279a2f7f |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 10, 2026, noon