Triple
T36467441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RLISP |
E898458
|
entity |
| Predicate | extensionLanguageOf |
P105435
|
FINISHED |
| Object | REDUCE computer algebra system |
—
|
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: REDUCE computer algebra system | Statement: [RLISP, extensionLanguageOf, REDUCE computer algebra system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionLanguageOf Context triple: [RLISP, extensionLanguageOf, REDUCE computer algebra system]
-
A.
supportsExtensionLanguage
chosen
Indicates that one entity provides compatibility with or functionality for a specified extension language used by another entity.
-
B.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
C.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
-
D.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
E.
extensionName
Indicates the specific name assigned to an extension associated with an entity or resource.
- F. None of above.
Provenance (3 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.