Triple
T27637791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TypeScript standard library typings |
E696512
|
entity |
| Predicate | definesTypesFor |
P169058
|
FINISHED |
| Object |
RegExp API
The RegExp API is JavaScript’s built-in regular expression interface for pattern matching and text manipulation, providing objects, methods, and syntax to search, test, and replace strings based on regex patterns.
|
E1783601
|
NE 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: RegExp API | Statement: [TypeScript standard library typings, definesTypesFor, RegExp API]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RegExp API Triple: [TypeScript standard library typings, definesTypesFor, RegExp API]
Generated description
The RegExp API is JavaScript’s built-in regular expression interface for pattern matching and text manipulation, providing objects, methods, and syntax to search, test, and replace strings based on regex patterns.
Provenance (5 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f73a3c73cc81908477f85f697457d0 |
completed | May 3, 2026, 12:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12da8d4a3c8190a5d96dddf2d26972 |
completed | May 24, 2026, 11:01 a.m. |
| NEDg | Description generation | batch_6a12dbdc81948190b273567639a905cd |
completed | May 24, 2026, 11:07 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a12dc453c5c819094d51c46c94b5905 |
completed | May 24, 2026, 11:08 a.m. |
Created at: April 27, 2026, 2:24 p.m.