Triple
T33316815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMHomeManager |
E853036
|
entity |
| Predicate | adoptsProtocol |
P35980
|
FINISHED |
| Object | NSCopying |
—
|
NE NERFINISHED |
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: NSCopying | Statement: [HMHomeManager, adoptsProtocol, NSCopying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptsProtocol Context triple: [HMHomeManager, adoptsProtocol, NSCopying]
-
A.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
B.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
-
C.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
D.
parentProtocol
Indicates that one protocol serves as the direct ancestor or higher-level specification from which another protocol is derived or extended.
-
E.
negotiatesProtocolUsing
Indicates that one entity establishes or conducts a negotiation process with another entity using a specified protocol as the communication or agreement mechanism.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:33 a.m.