Triple
T9675039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA Triton Inference Server |
E234124
|
entity |
| Predicate | repositoryUrl |
P89567
|
FINISHED |
| Object | https://github.com/triton-inference-server/server |
—
|
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/triton-inference-server/server | Statement: [NVIDIA Triton Inference Server, repositoryUrl, https://github.com/triton-inference-server/server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryUrl Context triple: [NVIDIA Triton Inference Server, repositoryUrl, https://github.com/triton-inference-server/server]
-
A.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
-
B.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
C.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
-
D.
repositoryType
Indicates the kind or classification of a repository associated with an entity.
-
E.
repositoryDirectoryName
Indicates the name assigned to the directory in which a repository is stored or organized.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6d6dd48190a77c486337a58cb6 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.