Triple
T23394539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R4RS |
E559317
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | R5RS |
—
|
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: R5RS | Statement: [R4RS, successor, R5RS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: R5RS Context triple: [R4RS, successor, R5RS]
-
A.
R6RS
R6RS is the sixth revision of the Scheme programming language standard, defining its core language features, libraries, and semantics.
-
B.
R4RS
R4RS is the fourth revised report on the Scheme programming language standard, defining its core syntax, semantics, and standard procedures.
-
C.
R3RS
R3RS is the third revision of the Revised^n Report on the Algorithmic Language Scheme, specifying a standardized version of the Scheme programming language.
-
D.
RnRS
RnRS is the standard specification document series that formally defines the Scheme programming language.
-
E.
Scheme R5RS
chosen
Scheme R5RS is the fifth revised report of the Scheme programming language standard, defining its core syntax, semantics, and standard libraries.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a49eb3b881909da7f1c47c67c81f |
completed | April 29, 2026, 6:26 a.m. |
Created at: April 17, 2026, 5:36 p.m.