Triple
T15361451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ResNeXt |
E367297
|
entity |
| Predicate | hasCodeRepository |
P19959
|
FINISHED |
| Object | https://github.com/facebookresearch/ResNeXt |
—
|
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/facebookresearch/ResNeXt | Statement: [ResNeXt, hasCodeRepository, https://github.com/facebookresearch/ResNeXt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodeRepository Context triple: [ResNeXt, hasCodeRepository, https://github.com/facebookresearch/ResNeXt]
-
A.
hasRepository
chosen
Indicates that an entity maintains or is associated with a specific repository (such as a code, data, or content store).
-
B.
hasPackageRepository
Indicates that an entity is associated with or provides access to a specific software package repository.
-
C.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
D.
hasCodeSpace
Indicates that an entity is associated with a particular code space or coding namespace in which its identifiers or codes are defined.
-
E.
hasCodeBrowser
Indicates that an entity provides or is associated with a tool or interface for browsing and viewing source code.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4607408190ab281a7f7a8012d3 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.