Triple
T22982829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R6RS I/O system |
E571518
|
entity |
| Predicate | providesProcedure |
P150487
|
FINISHED |
| Object | open-file-input-port |
—
|
LITERAL FINISHED |
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: open-file-input-port | Statement: [R6RS I/O system, providesProcedure, open-file-input-port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesProcedure Context triple: [R6RS I/O system, providesProcedure, open-file-input-port]
-
A.
procedureFeature
Indicates that a procedure possesses, involves, or is characterized by a particular feature or attribute.
-
B.
proceduresDefinedBy
Indicates that certain procedures are specified, established, or authored by a particular entity.
-
C.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
D.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
E.
typeOfProcedureHandled
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
- F. None of above. chosen
Provenance (4 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829645f88190aea1b96ea595ff60 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:49 p.m.