Triple
T29409056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SyncManager |
E745844
|
entity |
| Predicate | returnsFromGetTags |
P179228
|
FINISHED |
| Object | Promise |
—
|
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: Promise | Statement: [SyncManager, returnsFromGetTags, Promise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsFromGetTags Context triple: [SyncManager, returnsFromGetTags, Promise]
-
A.
returnsFromGetItem
Indicates that an entity is the value returned as a result of performing a "get item" retrieval operation on another entity.
-
B.
returnsFromRegister
Indicates that an entity retrieves or receives something back from a register or registry system.
-
C.
returnsFor
Indicates that an entity goes back to a previous place, state, or counterpart, typically reversing or completing an earlier departure or action.
-
D.
returnedFor
Indicates that an entity has been sent, given, or brought back in response to, or on behalf of, another entity or prior action.
-
E.
returnedAs
Indicates that one entity is given back or sent back to another entity or to its original source, typically as the outcome of a prior transfer, request, or operation.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 28, 2026, 2:56 p.m.