Triple
T7961202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitbucket |
E184867
|
entity |
| Predicate | supportsProgrammingArtifact |
P80037
|
FINISHED |
| Object | Git 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: Git repositories | Statement: [Bitbucket, supportsProgrammingArtifact, Git repositories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProgrammingArtifact Context triple: [Bitbucket, supportsProgrammingArtifact, Git repositories]
-
A.
supportsProject
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s project succeed.
-
B.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
C.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
D.
supportProgram
Indicates that one entity provides assistance, resources, or services through an organized program to benefit or aid another entity.
-
E.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b8256dc8190a4b73df7aded9097 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:12 p.m.