Triple
T28616381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CreateSemaphore |
E724281
|
entity |
| Predicate | handleReleaseFunction |
P116467
|
FINISHED |
| Object | ReleaseSemaphore |
—
|
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: ReleaseSemaphore | Statement: [CreateSemaphore, handleReleaseFunction, ReleaseSemaphore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handleReleaseFunction Context triple: [CreateSemaphore, handleReleaseFunction, ReleaseSemaphore]
-
A.
handledReleaseOf
chosen
Indicates that one entity managed, oversaw, or was responsible for carrying out the release of another entity (such as a product, version, or document).
-
B.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
C.
memberOfRelease
Indicates that an entity belongs to or is included within a specific release version or release package.
-
D.
freeRelease
Indicates that one entity releases another from an obligation, constraint, or state without requiring payment or compensation.
-
E.
frameFunction
Indicates that one entity serves as a functional or structural frame that supports, constrains, or organizes another entity or process.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 4:32 a.m.