Triple
T17677371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clojure core.async |
E440673
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | core.async |
—
|
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: core.async | Statement: [Clojure core.async, abbreviation, core.async]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: core.async Context triple: [Clojure core.async, abbreviation, core.async]
-
A.
Clojure core.async
chosen
Clojure core.async is a Clojure library that provides asynchronous programming primitives like channels and go blocks to enable CSP-style concurrent and parallel programming.
-
B.
Clojure
Clojure is a modern, functional, and dynamic dialect of Lisp that runs on the Java Virtual Machine and emphasizes immutability and concurrent programming.
-
C.
ClojureScript
ClojureScript is a dialect of Clojure that compiles to JavaScript, enabling functional, Lisp-style programming for web and other JavaScript-based environments.
-
D.
Kotlin coroutines
Kotlin coroutines are a concurrency framework in the Kotlin language that simplify writing asynchronous, non-blocking code using a structured, sequential style.
-
E.
join-calculus
Join-calculus is a process calculus designed for specifying and reasoning about concurrent and distributed systems, emphasizing message-based synchronization and mobility.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 10:01 a.m.