Triple
T17569240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sequence (Swift protocol) |
E427891
|
entity |
| Predicate | elementAccessPattern |
P79849
|
FINISHED |
| Object | single-pass iteration |
—
|
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: single-pass iteration | Statement: [Sequence (Swift protocol), elementAccessPattern, single-pass iteration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementAccessPattern Context triple: [Sequence (Swift protocol), elementAccessPattern, single-pass iteration]
-
A.
accessPattern
chosen
Indicates how an entity interacts with or retrieves data or resources, such as the manner, frequency, or sequence of access.
-
B.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
C.
accessPath
Indicates a path, route, or means by which something can be reached, entered, or accessed.
-
D.
accessDirection
Indicates the direction or orientation from which access to something is obtained or permitted.
-
E.
accessStructure
Indicates that one entity has the ability, permission, or means to reach, use, or interact with the structure represented by the other entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.