Triple
T265165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TypeScript |
E5705
|
entity |
| Predicate | repository |
P409
|
FINISHED |
| Object | https://github.com/microsoft/TypeScript |
—
|
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: https://github.com/microsoft/TypeScript | Statement: [TypeScript, repository, https://github.com/microsoft/TypeScript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repository Context triple: [TypeScript, repository, https://github.com/microsoft/TypeScript]
-
A.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
B.
depositary
Indicates that one entity holds or safeguards something (such as assets, documents, or funds) on behalf of another entity.
-
C.
recall
Indicates that an entity retrieves or brings back into awareness information, events, or items that were previously known, experienced, or stored.
-
D.
department
Indicates that one entity functions as an organizational unit or division within another, typically larger, entity.
-
E.
recurs
Indicates that an event, condition, or pattern happens again, often repeatedly or at regular intervals, after having occurred before.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.