Triple
T27755558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUnknown |
E701323
|
entity |
| Predicate | lifetimeManagedBy |
P107490
|
FINISHED |
| Object | AddRef and Release |
—
|
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: AddRef and Release | Statement: [IUnknown, lifetimeManagedBy, AddRef and Release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeManagedBy Context triple: [IUnknown, lifetimeManagedBy, AddRef and Release]
-
A.
lifetimeControlledBy
Indicates that the existence or duration of one entity is dependent on and ends with the controlling entity’s lifetime.
-
B.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
C.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
-
D.
lifetimeRequirement
Indicates that one entity imposes or must satisfy a specified duration or lifespan condition in relation to another entity or context.
-
E.
lifecycleManagedBy
chosen
Indicates that the entire lifecycle of an entity (such as its creation, updates, and retirement) is overseen or controlled by 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63760b350819088f0eca0257ca125 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:23 p.m.