Triple
T17569259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sequence (Swift protocol) |
E427891
|
entity |
| Predicate | iterationOrder |
P73437
|
FINISHED |
| Object | defined by conforming type |
—
|
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: defined by conforming type | Statement: [Sequence (Swift protocol), iterationOrder, defined by conforming type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iterationOrder Context triple: [Sequence (Swift protocol), iterationOrder, defined by conforming type]
-
A.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
isOrderOf
chosen
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
C.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
D.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
-
E.
selectionOrderAdjustment
Indicates a modification to the original order in which items or options were selected, such as reordering or adjusting their selection sequence.
- 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.