Triple
T29409058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SyncManager |
E745844
|
entity |
| Predicate | registerResolvesTo |
P66401
|
FINISHED |
| Object | SyncRegistration |
—
|
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: SyncRegistration | Statement: [SyncManager, registerResolvesTo, SyncRegistration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerResolvesTo Context triple: [SyncManager, registerResolvesTo, SyncRegistration]
-
A.
resolvesTo
chosen
Indicates that one entity is mapped, translated, or evaluated into another specific entity as its target or result.
-
B.
resolves
Indicates that one entity successfully finds a solution, answer, or outcome for a problem, conflict, or uncertainty involving another entity.
-
C.
resolvesOver
Indicates that one entity successfully addresses, settles, or overcomes an issue, conflict, or obstacle involving another entity or context.
-
D.
linkedToResolution
Indicates that something is associated with, or directly connected to, a specific resolution or decision outcome.
-
E.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 2:56 p.m.