Triple
T26966745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL |
E679191
|
entity |
| Predicate | inputAccess |
P161388
|
FINISHED |
| Object | read-only input tape |
—
|
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: read-only input tape | Statement: [NL, inputAccess, read-only input tape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputAccess Context triple: [NL, inputAccess, read-only input tape]
-
A.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
inputIs
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
C.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
D.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
E.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621210b788190ab9e910cd635f366 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:36 a.m.