Triple
T17569118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Array (Swift) |
E427888
|
entity |
| Predicate | copySemantics |
P128034
|
FINISHED |
| Object | copy-on-write optimization |
—
|
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: copy-on-write optimization | Statement: [Array (Swift), copySemantics, copy-on-write optimization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copySemantics Context triple: [Array (Swift), copySemantics, copy-on-write optimization]
-
A.
copyType
Indicates that one entity is a copy or duplication of another, specifying the type or manner of that copying relationship.
-
B.
isCopiedBy
Indicates that an entity serves as the source from which another entity is duplicated or reproduced.
-
C.
hasCopy
Indicates that one entity possesses, contains, or maintains a duplicate or instance of another entity.
-
D.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
E.
coversMode
Indicates that one entity includes, addresses, or supports a particular mode or manner of operation associated with another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.