Triple
T5895379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozilla JavaScript team |
E131087
|
entity |
| Predicate | repositoryHostedOn |
P16030
|
FINISHED |
| Object | Mozilla source repositories |
—
|
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: Mozilla source repositories | Statement: [Mozilla JavaScript team, repositoryHostedOn, Mozilla source repositories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryHostedOn Context triple: [Mozilla JavaScript team, repositoryHostedOn, Mozilla source repositories]
-
A.
hostedOn
chosen
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
B.
repositoryName
Indicates the name assigned to a specific repository within a version control or storage system.
-
C.
repositoryType
Indicates the kind or classification of a repository associated with an entity.
-
D.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
E.
codeHostingService
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.