Triple
T29911338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCNAction |
E759680
|
entity |
| Predicate | usedByMethod |
P55465
|
FINISHED |
| Object | runAction(_:) on SCNNode |
—
|
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: runAction(_:) on SCNNode | Statement: [SCNAction, usedByMethod, runAction(_:) on SCNNode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByMethod Context triple: [SCNAction, usedByMethod, runAction(_:) on SCNNode]
-
A.
usedInMethod
chosen
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
B.
usedByClass
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
-
C.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
D.
usedByLine
Indicates that something (such as a resource, tool, or component) is utilized or operated by a particular line (for example, a production line, transit line, or code line).
-
E.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 6:10 p.m.