Triple
T17517226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP-IDF |
E426598
|
entity |
| Predicate | officialRepositoryURL |
P89567
|
FINISHED |
| Object | https://github.com/espressif/esp-idf |
—
|
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/espressif/esp-idf | Statement: [ESP-IDF, officialRepositoryURL, https://github.com/espressif/esp-idf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialRepositoryURL Context triple: [ESP-IDF, officialRepositoryURL, https://github.com/espressif/esp-idf]
-
A.
repositoryUrl
chosen
Indicates the web address where the related code, data, or resources are stored and managed in a version-controlled repository.
-
B.
officialRepositoryFor
Indicates that one entity serves as the primary, authoritative repository or source for another entity.
-
C.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
-
D.
stableReleaseRepository
Indicates that the referenced software artifact is stored in, or distributed through, a repository designated for stable (non-experimental) releases.
-
E.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.