Triple
T27728741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | API Blueprint |
E697372
|
entity |
| Predicate | canBeVersionControlledWith |
P9403
|
FINISHED |
| Object | Git |
—
|
NE NERFINISHED |
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 | Statement: [API Blueprint, canBeVersionControlledWith, Git]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeVersionControlledWith Context triple: [API Blueprint, canBeVersionControlledWith, Git]
-
A.
usesVersionControlSystem
chosen
Indicates that an entity employs a version control system to manage and track changes to its files or code.
-
B.
previouslySupportedVersionControlSystem
Indicates that an entity used to support a particular version control system in the past but no longer does so.
-
C.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
D.
versionControlledBy
Indicates that an item (such as a file, document, or resource) is managed and tracked under the change history of a specific version control system or repository.
-
E.
isExternalVersionOf
Indicates that one entity is a version or variant of another entity that exists or is maintained outside the primary or internal system or context.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 3:10 p.m.