Triple
T32117185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSCopying |
E820269
|
entity |
| Predicate | usedInPattern |
P195403
|
FINISHED |
| Object | value object pattern |
—
|
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: value object pattern | Statement: [NSCopying, usedInPattern, value object pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInPattern Context triple: [NSCopying, usedInPattern, value object pattern]
-
A.
usedInMatch
Indicates that something (such as an item, tactic, or resource) was employed or utilized during a particular match or game.
-
B.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
C.
usedInMatchType
Indicates that something (such as a rule, item, or configuration) is applied or relevant within a specific type or category of match.
-
D.
usedInExpression
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
E.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: May 1, 2026, 12:28 a.m.