Triple
T32122899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Set (Swift) |
E820426
|
entity |
| Predicate | subscriptAccess |
P5872
|
FINISHED |
| Object | no index-based subscript |
—
|
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: no index-based subscript | Statement: [Set (Swift), subscriptAccess, no index-based subscript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subscriptAccess Context triple: [Set (Swift), subscriptAccess, no index-based subscript]
-
A.
requiresSubscript
Indicates that one element must be written with a subscript in relation to another element for proper notation or interpretation.
-
B.
offsetNotation
Indicates that one representation specifies how far and in what way another representation is shifted or displaced from a reference point or baseline.
-
C.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
D.
subsequentLettersIndicate
Indicates that the letters immediately following a given position or symbol convey or specify additional information related to that position or symbol.
-
E.
subrange
Indicates that one value or interval lies entirely within the bounds of another value or interval.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.