Triple
T32117172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSCopying |
E820269
|
entity |
| Predicate | invokedByMethod |
P9496
|
FINISHED |
| Object | -copy |
—
|
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 | Statement: [NSCopying, invokedByMethod, -copy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokedByMethod Context triple: [NSCopying, invokedByMethod, -copy]
-
A.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
B.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
C.
invokedByKey
Indicates that an action, event, or operation is triggered or initiated by a specific key input.
-
D.
createdByMethod
Indicates that something was produced, generated, or brought into existence through a specific method or procedure.
-
E.
calledBy
chosen
Indicates that one entity initiates a call or invocation to another 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_69f3490209c881908ec0241476715f15 |
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_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:28 a.m.