Triple
T22412936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol |
E554036
|
entity |
| Predicate | component |
P35
|
FINISHED |
| Object | Algol C |
—
|
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: Algol C | Statement: [Algol, component, Algol C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Algol C Context triple: [Algol, component, Algol C]
-
A.
Algol C
chosen
Algol C is the fainter tertiary star in the Algol triple star system, gravitationally bound to the close eclipsing binary that forms the well-known "Demon Star" in Perseus.
-
B.
Algol 68C
Algol 68C is a compiler implementation of the Algol 68 programming language, designed to translate its advanced structured constructs into executable machine code.
-
C.
Algol W
Algol W is a block-structured, high-level programming language designed by Niklaus Wirth as a successor to ALGOL 60, incorporating features that influenced the later development of Pascal and other languages.
-
D.
Algol 68 Genie
Algol 68 Genie is a modern, open-source implementation of the Algol 68 programming language designed for contemporary systems and practical use.
-
E.
Algol 68S
Algol 68S is a simplified subset of the Algol 68 programming language designed to make the language easier to implement and use.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1594496348190ba25dc0193d092f2 |
completed | April 29, 2026, 1:05 a.m. |
Created at: April 16, 2026, 8:46 p.m.