Triple
T28583963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timeout Detection and Recovery |
E723442
|
entity |
| Predicate | registryKey |
P165759
|
FINISHED |
| Object | TdrDelay |
—
|
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: TdrDelay | Statement: [Timeout Detection and Recovery, registryKey, TdrDelay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registryKey Context triple: [Timeout Detection and Recovery, registryKey, TdrDelay]
-
A.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
B.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
C.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
-
D.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
-
E.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 28, 2026, 4:16 a.m.