Triple
T22445246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Next 700 Programming Languages |
E554846
|
entity |
| Predicate | relatedConcept |
P37
|
FINISHED |
| Object | ISWIM |
—
|
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: ISWIM | Statement: [The Next 700 Programming Languages, relatedConcept, ISWIM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISWIM Context triple: [The Next 700 Programming Languages, relatedConcept, ISWIM]
-
A.
ISWIM
chosen
ISWIM is an influential early functional programming language design proposed by Peter Landin that introduced key concepts in lambda calculus–based languages and helped shape later languages like Scheme.
-
B.
SWIM
SWIM is a subsystem within the SARA framework, likely responsible for a specific functional module such as data handling, communication, or workflow management.
-
C.
SWI
SWI is the National Rail station code for Swindon railway station in Wiltshire, England.
-
D.
SWI
SWI is the FAA location identifier for Sherman Municipal Airport, a public airport serving Sherman, Texas.
-
E.
SWI
SWI is the stock ticker symbol for SolarWinds Corporation, a company known for developing IT infrastructure and network management software.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b46e8ac8190bfa8c611ffcba822 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 16, 2026, 8:47 p.m.