Triple
T5922368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expect.js |
E131728
|
entity |
| Predicate | originalRepository |
P33323
|
FINISHED |
| Object | https://github.com/LearnBoost/expect.js |
—
|
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/LearnBoost/expect.js | Statement: [Expect.js, originalRepository, https://github.com/LearnBoost/expect.js]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRepository Context triple: [Expect.js, originalRepository, https://github.com/LearnBoost/expect.js]
-
A.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
-
B.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
-
C.
originalServiceBranch
Indicates the military or organizational service branch in which an individual initially served or was first enlisted.
-
D.
officialRepositoryFor
chosen
Indicates that one entity serves as the primary, authoritative repository or source for another entity.
-
E.
originalRelease
Indicates the initial publication or first official release event of a work or product.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.