Triple
T36671561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BitBake |
E905428
|
entity |
| Predicate | supportsFetchProtocol |
—
|
GENERATED |
| Object | git |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFetchProtocol Context triple: [BitBake, supportsFetchProtocol, git]
-
A.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
C.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
D.
hasSubProtocol
Indicates that one protocol is a component, phase, or specialized part of another, more general protocol.
-
E.
supportsMultipleDataAndDisplayProtocols
Indicates that an entity is capable of handling more than one type of data protocol and more than one type of display protocol.
- F. None of above.
Provenance (1 batch)
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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.